Changes between Version 1 and Version 2 of HighLevelOverview


Ignore:
Timestamp:
Jan 11, 2013, 10:31:26 PM (6 years ago)
Author:
Shawn A. Wilson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HighLevelOverview

    v1 v2  
    11= High-Level Overview =
    22
    3 A shell for the web. But why? A shell provides a simple interface to computer resources. The shells you might be familiar with (BASH for *nix, MS-DOS's command.com, etc.) are all designed to interface primarily with resources only on the local computer, i.e. files and directories. But we now find ourselves in the connected age of the Internet yet our tools are lagging behind. Enter the IOVAR Web Shell, a shell designed for interfacing with resources across the web.
     3IOVAR Web Shell presently runs in Tomcat on Linux. Thus it has the privileges of the Tomcat user. It is written in Java and shell scripts. Note that even though many of these shell scripts may run in BASH just fine (since the syntax and command names are similar) they are not technically BASH scripts and so there is no guarantee that they will work in any shell but this one.
     4
     5Aside from parsing commands and executing jobs, part of a shell's function is to keep track of an environment for the user. This environment generally consists of current directory, typed-in command history, executable search path, and other shell-defined and user-defined variables. The IOVAR Web Shell is no different. However, since commands inputted and parsed on one server may in fact point to executables on a different server, there must be a mechanism by which the user's environment can be passed from one server to another. This is currently accomplished by making the environment available at /proc/shell/<hash> (where <hash> is automatically generated) and passing a reference to this location in an HTTP parameter named ''iosession''.