Hi Alexey, it all depends upon how sophisticated your AJAX app is and how easily you can re-create a particular state.
We add one or more "a name" targets with id's to the page. Whenever a significant state change happens within the app we update the name of the relevant target with a unique id (e.g. session_id-state_id) and then update the document location to that target (e.g. document.location = "#<session_id-state_id>"). It's also important to send this token to a server app to store this state information for retrieval when the page is loaded later (see below). Now, if the user bookmarks the page then they include this token that represents their state. This also lets them use the back and forward buttons/history. The tricky part is recreating that state when they load their bookmark and this depends upon how you've setup your application. Sometimes we have the server side application extract the target from the URL and pre-populate the state based on that. But for some other applications we just have the AJAX client do that once it's loaded. Of course this would generally mean that this URL/bookmark will always represent this specific application state - like a permalink. If you need this to change later you can just update the stored state that's mapped against this target/token...however you need to carefully think through the use cases for this. roBman On Tue, 2008-11-18 at 02:38 -0800, Alexey wrote: > Hello everybody > Is there a solution for bookmarking AJAX pages? > thanks > alex > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
