>The application server idea also has the problem of just how do
>you pass the necessary pieces of the CGI environment over there.
You create a request and response object. There are several design patterns
for this. The general pattern is a request object for the request
information and a response object which is just a output stream buffer.
Request object holds such elements as parameter collection, request specific
variable hash (J2EE), header parameters collection etc.. Here's a quick
little UML (sorta) diagram of an app server approach that mixes J2EE and ASP
object model.
Application
---------------
-globals [Hash <-- environment variables etc.]
---------------
-lock() <-- for locking Globals hash
-unlock()
+put( string, object )
+get( string )
+elements() <-- globals enumeration
---------------
Request
---------------
+headers
+parameters
---------------
Response
---------------
-buffer
-outputStream
---------------
+flush()
+write( string )
+write( char [] )
+write( int, char [] )
+write( int, int, char [] )
---------------
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
