At 11:26 AM 5/29/01 -0400, Chuck Esterbrook wrote:
>At 08:20 AM 5/29/2001 -0700, Mike Orr wrote:
>>But AsyncThreadedHTTPServer is also "experimental" and has its own
>>problems. (Remember how it timed out whenever I tried to log in to a
>>protected page?) So why not just give AsyncThreadedAppServer the
>>same status? Then just change the AppServer shell script to launch
>>ThreadedAppServer instead of AsyncThreadedAppServer.
I'll bet some of the problems in AsyncThreadedHTTPServer would be easier to
fix using ThreadedAppServer as the base instead of Async, just because it's
simpler. It'll just take somebody's time to do the rewrite.
>That's fine for the very short term, but what I'm really getting at is
>that I want to axe the async code out of the repository. It sucks up time
>and energy but doesn't seem to pay off. It was good to try it out to learn
>from it, but the lesson seems to be over.
>
>Another problem is that there is still duplication between the various app
>servers. So if I change the verbose mode, for example, I think it has to
>be changed in at least 2 places. That's no good.
>
>I'm interested in hearing objections to Async disappearing completely.
No objection, just wait until someone has time to switch the HTTP server to
Threaded before completely axing the code. I _might_ have time to do it
but I'd love for someone else to step up and give it a shot.
--
- Geoff Talvola
[EMAIL PROTECTED]
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
