It's already been done, twice.  First, WebKit 0.5 came with a buggy 
HTTPServer that was removed from the 0.6 version as it was built on 
the equally buggy AsyncThreadedAppServer that was also removed.  
Second, I've been working on an experimental version of Webware that 
I hope can serve as a base for creating the 0.7 release.  It includes 
a simple builtin HTTPServer that works pretty much as you describe it 
below.

You can access the code at:
http://sourceforge.net/cvs/?group_id=41909

The README at 
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/expwebware/Webware/README
has all the details.


Also note that this issue was discussed extensively a few weeks ago 
on the list and many people favoured bundling the xitami web server 
with Webware rather than supporting our own concoction.  Personally, 
I prefer a simple builtin server for development and testing use and 
Apache for deployment.

Cheers,
Tavis

On Saturday 15 December 2001 09:03, Ng Pheng Siong wrote:
> 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.)

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

Reply via email to