[Seaside] Something seaside developers need to be aware of

[Benjamin Pollack]

I strongly agree with Joe Gregorio that this is a bug with web
developers and not GWA [1]. HTTP GET should be idempotent.
Unfortunately, buttons are ugly and there's no easy way I know of to
make links that generate POST requests. There are two "easy"
solutions: add an anchorButtonWithAction: method that uses JavaScript
to make text look like a link but generate a POST request (this is
what Gmail does, incidentally) or patch Seaside to block GWA by
default. The first option is annoying, slightly klugy, and also the
most "correct" solution, in my opinion, but the second might be a
quick hack to solve the problem until we get a better solution.

--Benjamin

[1] http://bitworking.org/news/I_m_sorry__I_can_t_kiss_it_and_make_it_better_

On 5/6/05, Blanchard, Todd <tobl at amazon.com> wrote:
>           
> 
> http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php   
> 
> Google's web accelerator seems like a good thing for the public web, but it can wreak havok on web-apps and other things with admin-links built into the UI. How's that?  
> 
> The accelerator scours a page and prefetches the content behind each link. This gives the illusion of pages loading faster (since they've already been pre-loaded behind the scenes). Here's the problem: Google is essentially clicking every link on the page — including links like "delete this" or "cancel that." And to make matters worse, Google ignores the Javascript confirmations. So, if you have a "Are you sure you want to delete this?" Javascript confirmation behind that "delete" link, Google ignores it and performs the action anyway.  
> 
> We discovered this yesterday when a few people were reporting that their Backpack pages were "disappearing."  
>     
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
> 
> 
>