I just looked at the code as well as some ISAPI code from the Java app server I was running.
Its interesting, I just assumed that Webware would support keeping a socket open.
I agree with the timing issue, there are no problems with speed when I take to firewall out of the loop. Pretty much the normal
speed bottleneck is the database query itself, so my issue is really outside of Webware, I was just looking to Webware to fix it.
I'll try the isapi dll anyway and report back. This is an NT shop and thier web applications are pretty much all local B2B and only
accessed during the day, so they have some good automated server reboot procedures.
----- Original Message -----
From: "Tavis Rudd" <tavis@...>
To: "Geoffrey Talvola" <gtalvola@...>; "Aaron Held" <aaron@...>; "Geoffrey Talvola" <gtalvola@...>;
"Love, Jay" <Jay.Love@...>; <webware-devel@...>
Sent: Saturday, January 12, 2002 2:51 PM
Subject: Re: RE: [Webware-devel] I need a favor and a compiled isapi dll
> On Saturday 12 January 2002 06:36, Geoffrey Talvola wrote:
> > On Friday January 11, 2002 06:04 pm, Aaron Held wrote:
> > > > Why would the firewall slow down wkcgi.exe any more than the
> > > > ISAPI filter does? As far as the socket connections are
> > > > concerned, I think they pretty much do the same thing --
> > > > establish a new socket connection for each request.
> > >
> > > I was hoping that the .dll would reuse open sockets and not
> > > completely close them out each time.
> > >
> > > I honestly did not check.
> > Sounds like that would be a nice enhancement, both for the ISAPI
> > and for the mod_webkit and mod_python adapters. Could you add this
> > to the Wiki wisklist?
> At first glance, I think this would be incredibly difficult to do
> with Webware 0.6 or the experimental stuff I've been working on. It
> would involve very major refactoring, unless you were to use an
> intermediate dispatcher process that sits behind the
> firewall,maintains connections with the adaptor and fires off a
> socket connection to WebKit for each new request.
> There's probably easier things to change that will have more of a
> performance impact.
> Webware-devel mailing list