[Seaside] Re: Why could a POST take too much?
pdebruic at gmail.com
Mon May 12 22:07:47 UTC 2014
Just for clarity:
It doesn't have to be in a form. You can use jQuery to serialize the form
data using an ajax POST e.g.
html jQuery post serializeForm:(html jQuery id: 'myForm')
or with a GET
html jQuery ajax serializeForm:(html jQuery id: 'myForm')
You can also serialize arbitrary divs if you want using jQuery with
#serialize: and friends.
But I agree with everything else you've said.
Sven Van Caekenberghe-2 wrote
> On 12 May 2014, at 23:16, Mariano Martinez Peck <
> > wrote:
>> Could you explain what is the first POST and which is the second GET?
> This is basic Seaside 101: your navbar's button is inside a form (has to
> be), hence you submit the form, which is a POST. Seaside always replies
> with a redirect to a GET to get the _s and _k parameters in the URL. You
> can think of the first fase as callback processing and the second fase as
> Are you sure that the handling of the button's action (in your own code)
> does not take a lot of time by itself (apart from what Seaside does) for
> some application specific reason ?
> seaside mailing list
> seaside at .squeakfoundation
View this message in context: http://forum.world.st/Why-could-a-POST-take-too-much-tp4758452p4758816.html
Sent from the Seaside General mailing list archive at Nabble.com.
More information about the seaside