[Seaside] Why could a POST take too much?

Sven Van Caekenberghe sven at stfx.eu
Mon May 12 21:48:42 UTC 2014


On 12 May 2014, at 23:16, Mariano Martinez Peck <marianopeck at gmail.com> 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 rendering.

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 ?


More information about the seaside mailing list