To experiment with the feature set, as opposed to the actual speed, it
might be best to start with WebKit.cgi (or probably just Adapter.py),
and then port to mod_webkit. Actually, it might work okay for speed
too, since you'd still have balancing -- the front box would just have
to be beefier.
There was talk of associating users with particular instances of the
AppServer, via the SID, so that session data didn't have to be shared.
This would be a nice feature, and probably pretty easy to implement in
And, not to abort these ideas at all, there's also that Zope balancer
that sounds very interesting -- particularly in taking the SSL load off
the AppServer machines while doing balancing at the same time... and
then if you added caching to the mix, that would be a very nice
On Mon, 2002-07-01 at 12:37, Terrel Shumway wrote:
> On Sun, 2002-06-30 at 12:21, Bobby Kuzma wrote:
> > Is there anyone actively working on reworking mod_webkit to support multiple
> > AppServer instances, as described in the Wiki. I'd like to try implimenting
> > it, but I don't want to step on anyone elses toes in doing so.
> I did a patch to mod_webkit some time ago that would do a very simple
> round-robin among multiple servers. It may or may not be useful as a
> starting point. I am pretty rusty with C, and this was the very first
> apache module I worked on.
> -- Terrel
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> Webware-devel mailing list