Hi,

I'm thinking of writing my next web app in Webware. But before I do that,
first I want to muck around with the framework. ;-)

Here's my understanding of the "standard" WebKit architecture, based on
perusing the source:

        http client
            | 
            |
        http server
            |
            | *Adapter.transactWithAppServer()
            |
        ThreadedAppServer
            +
            + dispatchRawRequest()
            +
        Application

The http server runs in one process. ThreadedAppServer + Application run in
another process.


I want to try the following:

1. Craft a ThreadingHTTPServer from Base/SimpleHTTPServer. 

2. Craft a WebKitRequestHandler for said ThreadingHTTPServer. This handler
will package a http request into the appropriate format (borrowing code
from CGIHTTPServer), then dispatchRawRequest().

Thus, the architecture becomes:

        http client
            |
            |
        ThreadingHTTPServer 
            + 
            +
        AppServer 
            + 
            + dispatchRawRequest()
            +
        Application

(It also appears possible to use Medusa's or Twisted's http server in place
of ThreadingHTTPServer.)


I have these objectives in mind:

1. Run the http server and the app server in the same process. 

2. Make it possible to work with Webware with just Python and Webware,
i.e., without an external http server.

3. For the fun of it.


What do you think? Any gotchas I fail to notice, e.g., threading/locking
issues in the bowels of AppServer/Application when fronted by a concurrent
http server?

TIA. Cheers.

(I'm not subscribed. Please cc replies. Thanks.)
-- 
Ng Pheng Siong <[EMAIL PROTECTED]> * http://www.netmemetic.com


_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to