[Seaside] Disable a submit button

[Julian Fitzell]

The same thing should happen.  Seaside will only accept the processing 
of that submit button once.  The two clicks would have to be processed 
sequentially since only one request can be active in a session at a 
time.  That means the second the click would be treated exactly the same 
as if the user had come back to the page and clicked it again.

Julian

Pablo Iaría wrote:
> It might be the seaside way to solve that problem, but what if the user doubleclicks the submit button ?
> 
> 
> 
> 
> 
> On Thu, 24 Jul 2003 11:16 , Nevin Pratt <nevin at smalltalkpro.com> sent:
> 
> 
>>
>>Julian Fitzell wrote:
>>
>>
>>>Can't you just put that page in a seaside transaction?  Then after 
>>>they click the button, even if they go back and click on the button, 
>>>it won't do anything - they'll get redirected to the most recent page 
>>>in the session again.  This is assuming you are taking the approach 
>>>that you discussed of doing the payment submission server-to-server, 
>>>rather than having the user submit a form to to the payment site, of 
>>>course.
>>>
>>>Julian
>>
>>
>>You do that via the 'self session isolate:' approach that Derek mentioned?
>>
>>Today's a big Utah holiday-- gotta go with the family right now.  I'm 
>>planning on toying with Derek's suggestion later tonight.
>>
>>Thanks all!
>>
>>Nevin
>>
>>-- 
>>Nevin Pratt
>>Bountiful Baby
>>http://www.bountifulbaby.com
>>(801) 992-3137
>>
>>
>>
>>_______________________________________________
>>Seaside mailing list
>>Seaside at lists.squeakfoundation.org
>>http://lists.squeakfoundation.org/listinfo/seaside
> 
> 
> 
> 
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside