I understand what you are saying but it's not about the framework, but about the stateless nature of the web (in fact of the http protocol). Some places in a web applications do need a state to be displayed and loaded correctly. I think it is important to support quick access to data in form of bookmarks on a read-only page, wich is stateless in essence. It is quite similar to opening a document directly in open office.
What I was trying to say is most parts of an application are *stateful* and unless you save everything (or a persistent session identifier) in a cookie or in the url, you can't retrieve the state of the system at a precise moment. For the stateless part of an applications, I always try to give some quick accesses but until http is replaced by a connected protocol, I don't think it's possible to allow bookmarks everywhere in your application and expect everything to be coherent. Of course, I can be wrong! On 12/21/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > On 12/21/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > I think bookmarks are a bad idea in web applications even when not built > > with Ajax. After all, an application is stateful and need a *state* to run. > > Bookmarks in my mind are made for informational sites wich are staless and > > not applications. Do you expect to be able to return in a precise windows in > > a desktop application like Open Office for exemple? > > In my opinion, this type of reasoning is flawed. You should not limit > applications in one platform only to what another platform provides. > This is like saying colored TV programs should not worry about how the > colors look because radio programs don't even provide images. They > are different mediums, different platforms, with different > characteristics. Each will have different capabilities, and being > able to go to a specific page is a basic an ability of web > applications. > > Besides, I may not expect to launch Open Office in a precise dialog > box, but if I know I want to open a specific document in open office, > I want the ability to double click on that document and have it open > right away. I don't want to go through several windows and dialog > boxes to search for something I already have in my sight. > > Just because you're using a framework that makes it harder to support > what should be basic functionality provided by the environment you're > in, doesn't make supporting it a bad idea. > > Earlier Struts versions made it hard to do redirects with parameters. > The solution is not to spread a gospel that said "redirects with > parameters are bad", the solution is to provide support for it in the > framework. > > Hubert > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
