You're right: We checked the Apache log and the user just double clicked. But Netscape seems to have a bug that cannot be handled with the JavaScript solution: If you have your security settings in a way that he comes up with a messagebox before sending out POSTs, he sometimes "overhears" the first click in that box and only reacts on the second click. Strangely he then also sends out 2 requests. How does the JavaScript to catch this kind of doble clicks look like? Thanks for your help ona rainy saturday, -- Till. -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Samstag, 18. November 2000 16:21 An: [EMAIL PROTECTED] Betreff: Re: One user -> 2 parallel threads So, in those cases, I've built JavaScript logic running in the browser (in the HTML file) that will set a boolean flag to block the second (and subsequent) click(s). Is there a simple way to handle this server-side (I can imagine the hard ways!), or does anyone know that the client side still has holes I have not witnessed? JT << Undoubtedly the user clicked twice on the button or link and actually created two requests.>> > > Hi mail list, > > we encounter the following problem with Tomcat. From time to time a browser > request seems to be handled by two threads from tomcat in parallel. Our own > log from java servlets shows entries of different threads doing the same > task for the same user, wich are just some milli secs apart. >>
