Hallo,
Karl Putland hat gesagt: // Karl Putland wrote:
> On Sat, 2003-02-15 at 02:25, Frank Barknecht wrote:
> > I see another problem: I doubt, that the IP adress can fully identify
> > a user, if you have proxies or firewalls in between.
> Not to mention that an aol client changes IP addresses f
> I see another problem: I doubt, that the IP adress can fully identify
> a user, if you have proxies or firewalls in between.
A) Oops.
B) Dang.
C) Hmmm... I'm going to take the advice of kicking off the slow
process in a new thread, and returning a monitor page. In doing
so I will have the th
Hallo,
Ian Bicking hat gesagt: // Ian Bicking wrote:
> On Thursday, February 13, 2003, at 06:38 AM, James R. Phillips wrote:
> >I have the user's IP address for use in distinguishing different
> >users on different threads.
>
> Will this really work? I mean, will a browser keep sending data even
Nick Murtagh wrote:
Ian Bicking wrote:
Will this really work? I mean, will a browser keep sending data even
as its getting completed responses?
There are components in IE and Mozilla that allow you to make HTTP
requests manually using Javascript. You can even do asynchronous
requests.
Nick
Ian Bicking wrote:
Will this really work? I mean, will a browser keep sending data even as
its getting completed responses?
There are components in IE and Mozilla that allow you to make HTTP
requests manually using Javascript. You can even do asynchronous
requests.
Nick
On Thursday, February 13, 2003, at 06:38 AM, James R. Phillips wrote:
At http://zunzun.com, I have processes that can possibly take a
couple of minutes to complete. What I would like to do when
handling some of the browser requests is to immediately send
the user a status page, call the methods a
A couple of points:
It sounds like you would be changing a "transport" level function that
would need to be handled on the app level. If you need to write
javascript then it should correspond to servlet code. If you need to
write browser software it should correspond to HTTPServlet.
I have h
I need to extend ThreadedAppServer.RequestHandler.handleRequest(),
and would like to discuss doing so before embarking on the work.
As Webware is currently written a browser or XML-RPC request must
wait until all application-side processing of that request has
completed before receiving a finished
