Webware for Python

Terrel Shumway wrote:
> Another option, probably easier in both the short run and the 
> long run,
> is to find another similar module like mod_backhand that has already
> been ported, and write another adapter to connect to it:
>   pro: 
> 	let someone else maintain the icky C part,
> 	write the adapter in clean, sweet, elegant Python! 8-)
>   con:
>         may be a little more work dealing with non-webware specific
> stuff. (e.g. parsing the stream instead of marshal.loads())

Looks to me like mod_backhand is a load-balancing proxy module.  So it would
require WebKit to be an HTTP server.  But if WebKit is an HTTP server, then
you don't need mod_backhand at all, unless you need it for the
load-balancing features.  You could just use WebKit without Apache, or use
mod_proxy.

Unless I'm misreading what mod_backhand does.
http://www.backhand.org/mod_backhand/

- Geoff

Geoffrey Talvola wrote:
> Looks to me like mod_backhand is a load-balancing proxy 
> module.  So it would
> require WebKit to be an HTTP server.  But if WebKit is an 
> HTTP server, then
> you don't need mod_backhand at all, unless you need it for the
> load-balancing features.  You could just use WebKit without 
> Apache, or use
> mod_proxy.

Although I should point out that mod_webkit has the nice retry feature that
lets you restart WebKit without dropping any requests.  I'm pretty sure this
won't be possible with mod_proxy.  So even if WebKit grows an HTTP server at
some point, there will still be a good reason to keep mod_webkit around.

- Geoff