[Seaside] Seaside redirects, really?

Boris Popov, DeepCove Labs boris at deepcovelabs.com
Mon Oct 3 12:01:34 UTC 2011



Car and airplane crashes are also a bit of an exception case, yet so
much effort goes into development and testing of safety systems. I'm not
sure what your end game is in this thread? If you're trying to convince
the rest of us to remove the part of the framework that's important to a
lot of people, you likely will not succeed. But if you're trying to
understand the reasons for the redirect so you can make informed
decisions for your own applications, by all means.




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


On Oct 3, 2011, at 8:29 AM, Julian Fitzell wrote:

				Similarly the redirects serve a well

				thought purpose.


			which is what exactly?

			can you describe that well thought purpose?


		Decouple the callback processing from the rendering.

	Thus ensuring that (a) hitting refresh doesn't re-trigger an
	and (b) you don't get the browser dialog asking if you want to
	resubmit form data when you hit the Back button.


okay those are reasons.



for a: the refresh is an exception case, not the normal case, yet
everything gets penalized because of that?

for b: the browser opens that dialog only on POST requests only when the
user press the back button, again an exceptional case but seaside it's
penalizing every other request because of that?


sorry but that sounds right or "well thought" to you?


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




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

More information about the seaside mailing list