Changes between Version 2 and Version 3 of soc/2007/cgi/Concepts


Ignore:
Timestamp:
Jun 6, 2007, 2:54:59 AM (15 years ago)
Author:
Darren Garvey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • soc/2007/cgi/Concepts

    v2 v3  
    1717The data from the client is stored in the request. Keeping transport data - eg. associated connection, destination ip, source ip - separate/enclosed seems logical. These could be held in a context<> construct, as an idea (the word comes from WSGI, although it's used in a slightly different context (NPI) there.
    1818
    19 == !CommonGatewayResponse ==
     19== !CommonGatewayReply ==
    2020
    21 Simply contains headers and a response string. It is returned to the client via a call to ```response::send(request&)```.
     21Simply contains headers and a response string. It is returned to the client via a call to ```reply::send(request&)```.
    2222
    2323== Gateway ==
    … …  
    4040
    4141'''Roadmap''': Implement everything for cgi and fcgi protocols. scgi SHOULD be implemented, just as long as it doesn't stop the project from being completed.
     42
     43== Dispatcher ==
     44
     45A dispatcher receives events from the library and must act on them. It is agreed that it should be decoupled from the library core, but the details of the decoupling are still fuzzy.