[Seaside] Seaside redirects, really?

[Boris Popov, DeepCove Labs]

I say go for it if that's what you need in your app, there's clearly a
simple way of disabling them in your case, but I rather suspect this
won't become a default any time soon and for good reason IMHO.

 

-Boris

 

From: seaside-bounces at lists.squeakfoundation.org
[mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of
Sebastian Sastre
Sent: Wednesday, October 05, 2011 8:38 AM
To: Seaside - general discussion
Subject: Re: [Seaside] Seaside redirects, really?

 

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*.

 

sebastian <http://about.me/sebastianconcept> 

 

o/





*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/753180f7/attachment.htm