[Seaside] callbacks of disabled submit buttons

Sebastian Sastre ssastre at seaswork.com
Fri Aug 21 19:32:14 UTC 2009

> make it idempotent
> > until the result is received preventing silly server load.
> You are looking for read-only, I guess. The difference between
> disabled and read-only is described a bit above: http://bit.ly/4xG24Y.
That sounds about right. Figuring out how...

> > Another example is a "confirm purchase" kind of button 
> where a capture of money
> > is made.
> I wouldn't count on the we client, to make it secure you *have to*
> prevent a double confirmation on the server, for example by checking
> in your model or using #isolate:
> Cheers,
> Lukas

sure. What I mean is both. Actually is decided by the server but as an extra
measure I want additionally to prevent UI side excess of clicks.

Never bad to remember it anyway.

thanks for the pointer

More information about the seaside mailing list