connectors and servers (Re: [Webware-discuss] 8086 dual use)

[Terrel S. <tsh...@ic...>]

Chuck Esterbrook wrote:

> At 12:40 PM 4/18/2001 -0400, Geoff Talvola wrote:
> >This doesn't seem like the right long term solution.  A better mechanism
> >might allow you to just specify the port in
> >AsyncThreadedHTTPServer.config, with all other settings inherited from
> >AppServer.config.  But I don't have time to work on that right now.
>
> That's another possible solution as well. However, my "sharing" point
> regarding various directories would still need resolution. I don't know
> that we should encourage running multiple servers out of the same WebKit
> directory (with our current architecture).

The "architecture" could use some improvement, but I am working on a good solution that will work now and for the long term.  I am actively working on three issues:

    1) Provide an easy way to run multiple servers from the same code base, with a simple acquisition mechanism to specify default and specific configurations. (coding 30% complete)
    2) Extend the functionality of Monitor.py to be able to monitor these multiple servers, and possibly be used directly in /etc/rc.d/init.d. (idea phase)
    3) Extend mod_webkit to round robin through multiple servers and try to connect more than once. (coding 60% complete)

RE: mod_webkit.  My current hurdle is creating an AF_UNIX address (I have never done socket programming in C before).   Also, if anyone knows how to get apache to return an error document, that would be helpful.

Once I get it to pass a reasonable smoke test, I will post it for the brave to play with.