[Seaside] [2.8]Slow connection causes problem
carlg at libertybasic.com
Tue Jul 5 03:19:30 UTC 2011
> Hi Carl,
> How would you like Seaside to handle it?
> Is there a difference between this case and clicking on the link,
> waiting for the page to load, hitting the back button, and then
> clicking on a different link?
Since Seaside claims to insulate the programmer from such things, it should have some mechanism to deal with this. I recognize that this is a difficult problem, but if it can be solved nicely in the Seaside framework that would be great.
What happens is that if the connection is slow (or if my app responds too slowly, but this is not the case here) then it makes sense to be able to declare any action (or all the actions on a page or in an app, or for mobile browsers) as doable just once or maybe doable again after so many milliseconds or seconds. Then at least the developer can address the problem if needed.
I supposed I could implement this myself somehow in my coding style. How would you recommend this best be done?
On Mar 9, 2011, at 3:12 AM, Julian Fitzell wrote:
> On Tue, Mar 8, 2011 at 3:06 AM, Carl Gundel <carlg at libertybasic.com> wrote:
>> When I access my Seaside application using my iPhone over a 3G connection it is very easy to click on an anchor and then click on it or another anchor before I get a response. This often becomes a problem because the underlying state of my application is no longer valid for the second click. Clearly it makes sense for Seaside to handle this intelligently.
>> -Carl Gundel
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside