[Seaside] Seaside redirects, really?

Sebastian Sastre sebastian at flowingconcept.com
Wed Oct 5 12:37:54 UTC 2011

On Oct 4, 2011, at 2:26 PM, Norbert Hartl wrote:

> And still what you are saying is correct that whatever I tell you the extra request goes on top. I just want to add that the effect is not as big as you might think.
> Norbert

perhaps, but we should rely on the measured observations on how it performs with redirects vs. without them.

Probably not for everybody but there is something else: 

For all people using one transaction per request kind of architectures...

Having the redirect means that your app needs 2 transactions per action with all the overhead and complications that it could mean*.



*for example the data your app readed fresh in the first transaction has no use on the second complicating the app (if consistency is mandatory it probably requires a re-read). Depending on how the app deals with that problem, that could be a hidden cost (paid in latency in the magnitude of I/O and in development costs)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20111005/60e26b34/attachment.htm

More information about the seaside mailing list