W3C home > Mailing lists > Public > public-webapi@w3.org > November 2005

RE: Ajax Back/Forward History problem - saving document state by document.save()

From: Karl Pongratz <karlhp@karlhp.com>
Date: Wed, 23 Nov 2005 10:00:36 +0200
Message-ID: <438421A4.9090308@karlhp.com>
To: public-webapi@w3.org, bill@pointweb.net

>We have two scenarios here.  Mr. Heaton mentioned that the web doesn't go
>back and forth, but in all different directions.  We have discussed Gmail
>and Flicker.  We have discussed search engine compatibility, and mailing or
>bookmarking links.
>
>Be there are two different problems that need to be solved.  Mr. Eriksen
>puts it very well:
>
>"The concept of browsing the web and using web applications are very
>different."


I am not sure if you can make such a clear cut. Take i.e. Google Reader 
or Google Maps, they fit in my opinion into the browsing model, yet 
these are web applications. Or aren't they? In my opinion it really 
depends of the application type, Google Reader, Gmail and a CMS text 
editor are three different applications, each of them may need a 
different approach.

As a side note, a few month ago I said myself that the web browsing 
model doesn't work for web applications (not even for the simplest once) 
and that the Back button is evil, though a few fellows on the WHATWG 
list told me that browsing can perfectly fit for web applications. So I 
finally think yes, it could be manageable,  not for all application 
types but for many.

Karl
Received on Wednesday, 23 November 2005 08:00:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:52 GMT