1
IVLE - System Architecture
2
==========================
7
This document describes the high-level system architecture of IVLE,
8
specifically with respect to the "pluggable clients" interface.
10
Users and authorization
11
-----------------------
13
We need some way to authenticate users and store information about a logged-in
14
user. Whether they are stored in a database local to our system remains to be
17
Importantly, we need some way to send user information to the clients. This is
18
discussed in the "pluggable clients" section.
23
The IVLE system is largely just a collection of various components, called
24
"clients", such as the file browser, text editor, console, tutorial sheets,
27
The architecture provides a common interface in which clients can be plugged
30
Firstly, we want all HTML pages on the site to be generated with a common
31
header. The easiest way to do this is to write our own Python handler which
32
is common to the entire application (this replaces the standard handlers such
35
This top-level handler handles all authentication (for instance,
36
checking the session to see if a user is logged in properly and if not,
37
redirecting to the login page). It then outputs the header, and calls the
38
appropriate client based on the URL. The test of "whether the student is an
39
Informatics student" is considered part of the authentication layer. (So
40
students who are not enrolled in Informatics are treated the same way as a
43
Note that some clients ("login" and "exec") do not require authentication.
44
This will be one of the properties of the client in the global clients file.
46
Note that the handler does *not* perform authorization - that is left up to
49
One special feature of the handler will be the ability to write an XHTML
50
header (which includes the user's name and links to profile page, IVLE logo,
51
and tabs for all the clients). This is important to keep a consistent
52
interface between the clients. This header will be available upon request from
53
the client. It is up to the client to NOT request a header for non-HTML
54
content (or it will be ruined), and also not to request a header when
55
executing student's code (ie. the exec module will never request a header).
57
### Plugin interface ###
59
The top-level handler will keep a Python file (or a text, JSON, etc file)
60
containing a list of valid clients. This is a dictionary mapping clients'
61
internal names (the top-level directories, as described below in "URLs" and
62
the "planned clients") to some other date about the clients (such as a
63
friendly name to display in the tabs, and a boolean as to whether or not to
64
display the client in the tabs).
66
Part of the HTML header which the handler generates is a set of tabs linking
67
to all of the clients in this list, or at least the ones with "show in tabs"
68
turned on. Clients such as "exec" and "admin" will not have a tab.
70
Each client will be located physically in a directory "clients", in a
71
subdirectory of the client's name. (eg. the console is located in
72
"clients/console"). There *must* be a file in this directory called
73
**client.py**. This file is called by the handler for most requests.
75
All requests will go through the handler. Note that there is some media (such
76
as CSS, JavaScript and image files which are directly part of the application
77
itself), which we do not want to pass through the handler. These will be
78
placed in a special top-level directory, which Apache will be told to serve
79
directly. (eg. "/media").
81
This means that the contents of each client directory is a Python program
82
*only*, and contains no files accessible by the browser. It consists of
83
client.py, plus any Python files imported by client.py (but none of these
84
files will directly serve web content).
86
Inside client.py, there is a fixed interface which all clients must follow.
87
Firstly, there is a set of information which the handler must pass to the
88
client in numerous calls - such as username, URL, and nicely split up parts of
89
the URL such as the path, the GET variables, and also the POST data, as well
90
as mod_python's low-level Request object.
91
This information is encapsulated into an object and passed as a single
92
argument to the client handling functions.
94
Note that as stated above, the handler may need to insert HTML contents into
95
the output stream. Instead of having two separate function calls (a call to
96
find the mime type and a call to get content), we'll simply provide a wrapper
97
object to the client where the client can make callbacks to.
99
To this end, the client receives an object containing all of the information,
100
as well as an object with some methods to call. The handler passes this to a
101
function in client.py, `handle`. The callback object contains the following
104
* set_mime_type(string) - Sets the output mime type. May be called any number
105
of times (including 0, will default to HTML), but may not be called after
106
any writing has been done.
107
* set_status(string) - Sets the HTTP response status. The string is a numeric
108
code followed by a description, for example "404 File Not Found". May not be
109
called after any writing has been done.
110
* set_location(string) - Sets the Location field of the HTTP response to a new
111
URL. For use with 300-level HTTP response codes. May not be called after any
112
writing has been done.
113
* write_html_headers() - Writes the general site headers to the output stream.
114
May not be called after any writing has been done.
115
* write(string) - Writes raw data to the output.
117
Note that this is very similar to the CGI interface, but much higher level (we
118
have functions to call instead of writing strings, and we send the GET and
119
POST data in a packaged object instead of environment variables and stdin).
121
Note that, as with CGI, there is a "cutoff point" during the processing
122
(immediately when the first call to `write` or `write_html_headers` is made) -
123
in which the response headers are written to the server.
125
### Application directory hierarchy ###
127
Due to the handler, we have a nice property that the application directory
128
hierarchy is completely removed from the apparent hierarchy on the web. This
129
has two opportunities: we can call the applications (in their directory
130
hierarchy) a different name than the URL suggests, and also we can lay out the
131
directory hierarchy with developers interests in mind.
133
We capitalise on the first issue by mapping the "action" (url name) of a
134
client to the actual name. (Clients are indexed by url-name so they can
135
be looked up when a URL is requested).
137
The proposed application directory hierarchy is:
140
/clients - All clients go in here
141
/clients/myclient - "actual" names of the clients
142
/dispatch - Code files for the top-level dispatch
143
/dispatch.py - Entrypoint for the top-level dispatch
144
/media - Publically viewable files
145
(Note that this directory hierarchy maps onto the web site)
146
/media/myclient - media files specific to each client go in a subdir
147
/media/dispatch - media files for the top-level dispatch
148
/conf - Special .py files which hold configuration info (for the admin to
149
edit, not the programmers).
154
It would be good if we had full control of URLs and were able to make them
155
"nice" at all times. The criteria for "nice" URLs are as follows:
157
* The paths in the URLs reflect a sensible hierarchy of where you are in the
158
program at the current time.
159
* The URLs do not contain any file extensions for the pages (no .html or
160
.py), although linked files such as CSS, JavaScript and image files should
161
have appropriate file extensions.
162
* The URLs do not contain unnecessary garbage arguments, and preferably no GET
163
arguments at all (for instance, the file browser will specify the path to
164
browse in the actual URL path, not the GET arguments.
165
* The URL does not contain the student's login name. This is implicit in the
166
browser session. (This requirement allows for us to link to URLs in
167
documentation which will work for any student). (Note that URLs may contain
168
other students login names for browsing their work - this is determined by
169
the individual clients).
171
The top-level directory given in the URL determines the client which the
172
handler will pass off to. For instance,
174
http://www.example.com/ivle/console
176
Since IVLE is located at `http://www.example.com/ivle`, it will consider the
177
"top-level directory" to be "console", and therefore will call the client
178
whose action is "console". This may not be the actual name of the client. For
179
example, the "edit" action maps onto the "editor" client, while the "serve"
180
action maps onto the "exec" client. (Perhaps it is best for simplicity if
181
these do in fact correspond).
183
For another example, consider the file browser (action name "files"). The URL
184
may have subdirectories after it which indicate the path to explore. This will
185
be detailed in the clients section below. An example of a browse URL is:
187
http://www.example.com/ivle/files/jdoe/151/proj1/
189
In this instance, the handler will see the top-level directory as "files", and
190
will therefore link to the file browser client. The file browser client will
191
then receive the additional arguments passed to it in some way, which in this
192
case are "jdoe/151/proj1/". The file browser client will then handle this path
193
and serve up the correct directory.
195
### Relative URLs inside HTML content ###
197
It is a requirement that the application can be placed anywhere in a web
198
server's directory hierarchy, not just at the top level. This means HTML
199
should never contain absolute URLs (beginning with, eg, "/browse"). Then it
200
would need to be in the site root.
202
To solve the problem of how to generate URLs, one of the fields the handler
203
will pass into the clients (which it will read from a config file somewhere)
204
will be the "site root". This may be "/ivle", for instance. Therefore all
205
absolute URLs generated by the applications must be prepended with the "site
206
root". (In our case the site root will probably be "/", but it's a good
209
### Student's directory hierarchy, common code ###
211
Many clients share the concept of exploring the student's directory hierarchy,
212
as explained above for the browser module. The common code for handling the
213
student id or group name (etc) and authorization will be available as a
214
separate module for all such clients (browser, editor, exec) to use.
219
### File Browser, Text Editor and Executor ###
221
Three of the most important clients are the file browser ("browser"), text
222
editor ("editor") and executor ("exec"). These three share a commonality in
223
that they all access the student's directory hierarchy and files. They all
224
share a lot of code in common, and in particular, there is a common
225
server-side handler for file access, directory listings and subversion.
227
Firstly, every file and directory is classified into one of the following
228
categories (based on its inferred MIME type and possibly whether it contains
229
invalid Unicode characters):
234
4. Text file (unless it fits the above, eg, SVG files)
235
5. Any other binary file
237
How each of these is handled depends on which of the 3 clients is accessing
240
#### File Browser ####
246
1. Directory - Displays a directory listing (this is its primary purpose).
247
2. Image - Displays the image inside the main navigation interface.
248
3. Audio - (non-core) Provides a streaming audio player within the main
249
navigation interface.
250
4. Text file - Redirect to edit.
251
5. Binary file - Provides a download link within the main navigation
254
Note that no matter what, using browser will remain within the navigation
255
interface so you will never be "lost" inside a raw image or something. It also
256
will not throw binary files as downloads directly to you.
258
Note that the src of the image tag in (2) and the href of the download link in
259
(5) will simply be links to the exec version of the same file.
261
File browser will include the Python file which serves up JSON responses to
262
requests for directory hierarchies, and performs SVN and file access commands.
263
This file will be used by the text editor (at least) and possibly exec.
265
#### Text Editor ####
271
No matter what, editor provides a text area (with advanced editing
272
capabilities and syntax highlighting) for any file, even if it is binary. The
273
only exception is directories, which redirect to browser.
275
Note that it will not be possible to click into the editor for a binary file
276
(the browser will not offer an edit link). However, it will still be possible
277
to manually nav there, and then you handle the shock yourself.
283
Tab name: (not shown)
285
The executor is used to directly serve files out of a student's directory, as
286
if it was a standard web server. (It can be thought of as a little web server
287
inside IVLE). This means that:
289
* A whitelist of file types is kept which simply are served up raw. This
290
includes HTML, JavaScript, CSS, all reasonable image and audio formats, etc.
291
* Special "executable" file types (.py, .psp). Exec will call popen on a
292
Python process which loads a mod_python handler, cgihandler or psphandler on
294
* HTTP errors for banned files.
295
* When presented with a directory, it first tries to execute `__init__.py`
296
(the default item for the directory). It could also look for `index.html` or
297
`index.psp` if that failed. Failing that, it returns an HTTP 403 Forbidden
303
Action name: `console`
306
### Tutorial Pages ###
309
Action name: `tutorial`
312
### Administration ###
316
Tab name: (not shown)
318
Client checks authorization for admin status. Tab is not shown so students
319
will not normally know about this (but even if they find it they will be
326
Tab name: (not shown)
328
Authentication not required. Presents a login box.
330
Other similar clients are "logout" (which just immediately logs the current
331
user out and redirects to the main page), and "profile" (user settings).
added
removed
doc/notes/architecture.txt
