RE: Rép. : RE: Multi-click from the same user
another solution... make two layers...one for the form and one (waitlayer) with a text or image with something like "system is busy". after submit hide the layer of the form (and so also the buttons) and show the waitlayer. So one request is only possible. regards, Maarten -Oorspronkelijk bericht- Van: Antonio PAROLINI [mailto:[EMAIL PROTECTED] Verzonden: donderdag 7 juli 2005 17:50 Aan: tomcat-user@jakarta.apache.org; [EMAIL PROTECTED] Onderwerp: RE: Rép. : RE: Multi-click from the same user Hello, The previous poster (Mark) gives a solution where the server is no longer overloaded, but the second click makes the browser loose the result of the first click... Your proposal is the standard javascript solution, where you act on the GUI to avoid mutli-click. Maybe I should pick that one Very helpfull feedback, thanks all. Antonio >>> [EMAIL PROTECTED] 07/07 4:38 >>> The common way that this is achieved is similar to the previous poster. When a user clicks the button, you would actually move them to another page straightaway that spawns the 1 request thread and makes it very clear not to refresh the page. This is the strategy you can see with online booking services in particular like flights, holidays and so on, where it's essential that the user books once. > -Original Message- > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > Sent: 07 July 2005 15:26 > To: tomcat-user@jakarta.apache.org > Subject: Rép. : RE: Multi-click from the same user > > > Allistair, > > I have the same doubts you have... if the filter solution is not > enough, I'll try to dig deeper into the tomcat source to find out... > > Antonio > > >>> [EMAIL PROTECTED] 07/07 11:16 >>> > Your idea sounds like it makes sense but I can see that you may have > trouble, since even if you can identify a duplicate request, you will > have lost (I think) the request/response link on each subsequent click > of the button (which generates unique requests). I do not > think you'd be > able to connect an arbitrary request with a reponse that was intended > for an earlier request, but maybe I am wrong. > > Allistair > > > -Original Message----- > > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > > Sent: 07 July 2005 10:05 > > To: tomcat-user@jakarta.apache.org > > Subject: Multi-click from the same user > > > > > > Hello, > > > > We have a Struts intranet-web site running under tomcat 4.1.24. > > > > Some of the application function are pretty slow ( more than 10 > > secondes), and sometime users get mad and click 10 times on the same > > button. Tomcat raise 10 thread and on such slow operation, the > server > > can get very slowed down. > > > > Aside of javascript solutions ( blocking the button to be clicked > > twice), is there a tomcat configuration solution for this probleme ? > > > > I would imaging for instance, a HTTP connector that detect that the > > same call is being made by the same browser (or same > > UserPrincipal), to > > the same url with the same parameters , and instead of raising a new > > thread, wait for the 1 thread to end and returns its result ... Am I > > dreaming ? > > > > Thanks in advance for your help. > > > > Antonio Parolini > > > > > > > > > > > > > ** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please > notify > > the system manager. > > > > > ** > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --- > QAS Ltd. > Registered in England: No 2582055 > Registered in Australia: No 082 851 474 > --- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PR
RE: Rép. : RE: Multi-click from the same user
Hello, The previous poster (Mark) gives a solution where the server is no longer overloaded, but the second click makes the browser loose the result of the first click... Your proposal is the standard javascript solution, where you act on the GUI to avoid mutli-click. Maybe I should pick that one Very helpfull feedback, thanks all. Antonio >>> [EMAIL PROTECTED] 07/07 4:38 >>> The common way that this is achieved is similar to the previous poster. When a user clicks the button, you would actually move them to another page straightaway that spawns the 1 request thread and makes it very clear not to refresh the page. This is the strategy you can see with online booking services in particular like flights, holidays and so on, where it's essential that the user books once. > -Original Message- > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > Sent: 07 July 2005 15:26 > To: tomcat-user@jakarta.apache.org > Subject: Rép. : RE: Multi-click from the same user > > > Allistair, > > I have the same doubts you have... if the filter solution is not > enough, I'll try to dig deeper into the tomcat source to find out... > > Antonio > > >>> [EMAIL PROTECTED] 07/07 11:16 >>> > Your idea sounds like it makes sense but I can see that you may have > trouble, since even if you can identify a duplicate request, you will > have lost (I think) the request/response link on each subsequent click > of the button (which generates unique requests). I do not > think you'd be > able to connect an arbitrary request with a reponse that was intended > for an earlier request, but maybe I am wrong. > > Allistair > > > -Original Message- > > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > > Sent: 07 July 2005 10:05 > > To: tomcat-user@jakarta.apache.org > > Subject: Multi-click from the same user > > > > > > Hello, > > > > We have a Struts intranet-web site running under tomcat 4.1.24. > > > > Some of the application function are pretty slow ( more than 10 > > secondes), and sometime users get mad and click 10 times on the same > > button. Tomcat raise 10 thread and on such slow operation, the > server > > can get very slowed down. > > > > Aside of javascript solutions ( blocking the button to be clicked > > twice), is there a tomcat configuration solution for this probleme ? > > > > I would imaging for instance, a HTTP connector that detect that the > > same call is being made by the same browser (or same > > UserPrincipal), to > > the same url with the same parameters , and instead of raising a new > > thread, wait for the 1 thread to end and returns its result ... Am I > > dreaming ? > > > > Thanks in advance for your help. > > > > Antonio Parolini > > > > > > > > > > > > > ** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please > notify > > the system manager. > > > > > ** > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --- > QAS Ltd. > Registered in England: No 2582055 > Registered in Australia: No 082 851 474 > --- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Rép. : RE: Multi-click from the same user
The common way that this is achieved is similar to the previous poster. When a user clicks the button, you would actually move them to another page straightaway that spawns the 1 request thread and makes it very clear not to refresh the page. This is the strategy you can see with online booking services in particular like flights, holidays and so on, where it's essential that the user books once. > -Original Message- > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > Sent: 07 July 2005 15:26 > To: tomcat-user@jakarta.apache.org > Subject: Rép. : RE: Multi-click from the same user > > > Allistair, > > I have the same doubts you have... if the filter solution is not > enough, I'll try to dig deeper into the tomcat source to find out... > > Antonio > > >>> [EMAIL PROTECTED] 07/07 11:16 >>> > Your idea sounds like it makes sense but I can see that you may have > trouble, since even if you can identify a duplicate request, you will > have lost (I think) the request/response link on each subsequent click > of the button (which generates unique requests). I do not > think you'd be > able to connect an arbitrary request with a reponse that was intended > for an earlier request, but maybe I am wrong. > > Allistair > > > -Original Message- > > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > > Sent: 07 July 2005 10:05 > > To: tomcat-user@jakarta.apache.org > > Subject: Multi-click from the same user > > > > > > Hello, > > > > We have a Struts intranet-web site running under tomcat 4.1.24. > > > > Some of the application function are pretty slow ( more than 10 > > secondes), and sometime users get mad and click 10 times on the same > > button. Tomcat raise 10 thread and on such slow operation, the > server > > can get very slowed down. > > > > Aside of javascript solutions ( blocking the button to be clicked > > twice), is there a tomcat configuration solution for this probleme ? > > > > I would imaging for instance, a HTTP connector that detect that the > > same call is being made by the same browser (or same > > UserPrincipal), to > > the same url with the same parameters , and instead of raising a new > > thread, wait for the 1 thread to end and returns its result ... Am I > > dreaming ? > > > > Thanks in advance for your help. > > > > Antonio Parolini > > > > > > > > > > > > > ** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. If you have received this email in error please > notify > > the system manager. > > > > > ** > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --- > QAS Ltd. > Registered in England: No 2582055 > Registered in Australia: No 082 851 474 > --- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multi-click from the same user
how about this: http://java.sun.com/developer/EJTechTips/2003/tt0114.html Mark. --- Allistair Crossley <[EMAIL PROTECTED]> wrote: > Your idea sounds like it makes sense but I can see that you may > have trouble, since even if you can identify a duplicate request, > you will have lost (I think) the request/response link on each > subsequent click of the button (which generates unique requests). I > do not think you'd be able to connect an arbitrary request with a > reponse that was intended for an earlier request, but maybe I am > wrong. > > Allistair > > > -Original Message- > > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > > Sent: 07 July 2005 10:05 > > To: tomcat-user@jakarta.apache.org > > Subject: Multi-click from the same user > > > > > > Hello, > > > > We have a Struts intranet-web site running under tomcat 4.1.24. > > > > Some of the application function are pretty slow ( more than 10 > > secondes), and sometime users get mad and click 10 times on the > same > > button. Tomcat raise 10 thread and on such slow operation, the > server > > can get very slowed down. > > > > Aside of javascript solutions ( blocking the button to be clicked > > twice), is there a tomcat configuration solution for this > probleme ? > > > > I would imaging for instance, a HTTP connector that detect that > the > > same call is being made by the same browser (or same > > UserPrincipal), to > > the same url with the same parameters , and instead of raising a > new > > thread, wait for the 1 thread to end and returns its result ... > Am I > > dreaming ? > > > > Thanks in advance for your help. > > > > Antonio Parolini > > > > > > > > > > > > > ** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom > they > > are addressed. If you have received this email in error please > notify > > the system manager. > > > > > ** > > > > > > > - > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > --- > QAS Ltd. > Registered in England: No 2582055 > Registered in Australia: No 082 851 474 > --- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > Sell on Yahoo! Auctions no fees. Bid on great items. http://auctions.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-click from the same user
Try googling RequestControlFilter. You may be able to modify the code and check for a matching request from the sessionor use it as is...this may work for you. H - Original Message - From: "Antonio PAROLINI" <[EMAIL PROTECTED]> To: Sent: Thursday, July 07, 2005 9:05 PM Subject: Multi-click from the same user > Hello, > > We have a Struts intranet-web site running under tomcat 4.1.24. > > Some of the application function are pretty slow ( more than 10 > secondes), and sometime users get mad and click 10 times on the same > button. Tomcat raise 10 thread and on such slow operation, the server > can get very slowed down. > > Aside of javascript solutions ( blocking the button to be clicked > twice), is there a tomcat configuration solution for this probleme ? > > I would imaging for instance, a HTTP connector that detect that the > same call is being made by the same browser (or same UserPrincipal), to > the same url with the same parameters , and instead of raising a new > thread, wait for the 1 thread to end and returns its result ... Am I > dreaming ? > > Thanks in advance for your help. > > Antonio Parolini > > > > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > ** > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-click from the same user
Antonio PAROLINI wrote: Aside of javascript solutions ( blocking the button to be clicked twice), is there a tomcat configuration solution for this probleme ? You can use session context to store information that request is being processed by another thread and return quickly after another user click. Or maybe you can process such slow request in background thread reloading user page with some kind of a progress bar. -- Mikolaj Rydzewski <[EMAIL PROTECTED]> Becomo S.A. tel. (12) 2927104 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multi-click from the same user
Your idea sounds like it makes sense but I can see that you may have trouble, since even if you can identify a duplicate request, you will have lost (I think) the request/response link on each subsequent click of the button (which generates unique requests). I do not think you'd be able to connect an arbitrary request with a reponse that was intended for an earlier request, but maybe I am wrong. Allistair > -Original Message- > From: Antonio PAROLINI [mailto:[EMAIL PROTECTED] > Sent: 07 July 2005 10:05 > To: tomcat-user@jakarta.apache.org > Subject: Multi-click from the same user > > > Hello, > > We have a Struts intranet-web site running under tomcat 4.1.24. > > Some of the application function are pretty slow ( more than 10 > secondes), and sometime users get mad and click 10 times on the same > button. Tomcat raise 10 thread and on such slow operation, the server > can get very slowed down. > > Aside of javascript solutions ( blocking the button to be clicked > twice), is there a tomcat configuration solution for this probleme ? > > I would imaging for instance, a HTTP connector that detect that the > same call is being made by the same browser (or same > UserPrincipal), to > the same url with the same parameters , and instead of raising a new > thread, wait for the 1 thread to end and returns its result ... Am I > dreaming ? > > Thanks in advance for your help. > > Antonio Parolini > > > > > > ** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > ** > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --- QAS Ltd. Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multi-click from the same user
Hello, We have a Struts intranet-web site running under tomcat 4.1.24. Some of the application function are pretty slow ( more than 10 secondes), and sometime users get mad and click 10 times on the same button. Tomcat raise 10 thread and on such slow operation, the server can get very slowed down. Aside of javascript solutions ( blocking the button to be clicked twice), is there a tomcat configuration solution for this probleme ? I would imaging for instance, a HTTP connector that detect that the same call is being made by the same browser (or same UserPrincipal), to the same url with the same parameters , and instead of raising a new thread, wait for the 1 thread to end and returns its result ... Am I dreaming ? Thanks in advance for your help. Antonio Parolini ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
