I haven't finished reading this thread, but let me put me 2 cents in.
I am ready to switch to using Threaded as the default on both platforms.
The original purpose for Async was to make sure the AppServer didn't get
bogged down with any slow requests. As long as we are communicating through
a webserver, this isn't much of a problem, the reponse will be sent pretty
quickly. This isn't really the case when we are receiving a long put
request or sending a long response, as the webserver module is streaming the
reponse then, but I haven't really seen any problems crop up with this
situation. Async is definitely slower, and is more complicated.
With all that being said, I would like to keep the Async code in the
repository and maintain it. It is possible that at some point we will end
up needing its functionality, for any number of reasons. It is a well
documented server architecture, and many swear by it. Maybe our
implementation is off, or we just aren't pounding our servers hard enough.
Or maybe it isn't the right architecture for a "secondary" server like
AppServer. The point is, although I'm sure that we don't see the need for
it now, that may change in the future.
But, I can also maintain it locally just as easily, as I am the only one
with an interest in it. :)
Jay
----- Original Message -----
From: "Chuck Esterbrook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 29, 2001 11:26 AM
Subject: [Webware-devel] async
> 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.
>
> 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.
>
>
> -Chuck
>
>
> _______________________________________________
> Webware-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/webware-devel
>
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
