How can we save state of a GWT page?

[Rubina Paul]

 

 

We have one requirement to implement in GWT application. Below example will clear the requirement –

 

There are 3 screens in application. Suppose, user is on 2nd screen after moving from 1^st screen to 2nd screen. When user clicks on Next button on first screen, then some RPC call is executed and fetch data from some external database. This data is used to display on 2^nd screen. Now user bookmarks the browser URL (2^nd screen) and closes the browser window.

 

Next time, now user directly wants to navigate to the 2^nd screen without repeating the work done on 1^st screen. We want to store the state of 2^nd screen somehow on browser. If this screen launches, all Next and Previous button should also work properly.

 

Is this requirement achievable, if yes then which GWT APIs provides this feature? Please advice.

[Luigi Bifulco]

i think you could refer storage API from HTML5 spec. and wrapped since GWT 2.4... good work :).

For storage and synchronize pattern you can search in google for similar case studies.

I hope this was helpful.

Luigi

2012/7/26 Rubina Paul <er.pau...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "GWTEventService" group.
To view this discussion on the web visit https://groups.google.com/d/msg/gwteventservice/-/eQJl3R2z9dQJ.
To post to this group, send email to gwteven...@googlegroups.com.
To unsubscribe from this group, send email to gwteventservi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gwteventservice?hl=en.

[Luigi Bifulco]

Oh, i almost forgot 

https://developers.google.com/web-toolkit/doc/latest/DevGuideHtml5Storage 

this link join the client side storage world.

2012/7/26 Luigi Bifulco <bifulc...@gmail.com>

[Rubina Paul]

Hi,

The HTML5 Storage actually stores in string(key-value) pairs and it has limitations on storage limits.

 

 

On Friday, July 27, 2012 12:59:08 AM UTC+5:30, Luigi Bifulco wrote:

Oh, i almost forgot 

https://developers.google.com/web-toolkit/doc/latest/DevGuideHtml5Storage 

this link join the client side storage world.

2012/7/26 Luigi Bifulco <bifulc...@gmail.com>

i think you could refer storage API from HTML5 spec. and wrapped since GWT 2.4... good work :).

For storage and synchronize pattern you can search in google for similar case studies.

I hope this was helpful.

Luigi

2012/7/26 Rubina Paul <er.pau...@gmail.com>

 

 

We have one requirement to implement in GWT application. Below example will clear the requirement –

 

There are 3 screens in application. Suppose, user is on 2nd screen after moving from 1^st screen to 2nd screen. When user clicks on Next button on first screen, then some RPC call is executed and fetch data from some external database. This data is used to display on 2^nd screen. Now user bookmarks the browser URL (2^nd screen) and closes the browser window.

 

Next time, now user directly wants to navigate to the 2^nd screen without repeating the work done on 1^st screen. We want to store the state of 2^nd screen somehow on browser. If this screen launches, all Next and Previous button should also work properly.

 

Is this requirement achievable, if yes then which GWT APIs provides this feature? Please advice.

--
You received this message because you are subscribed to the Google Groups "GWTEventService" group.
To view this discussion on the web visit https://groups.google.com/d/msg/gwteventservice/-/eQJl3R2z9dQJ.

To post to this group, send email to gwteventservice@googlegroups.com.
To unsubscribe from this group, send email to gwteventservice+unsubscribe@googlegroups.com.

[Luigi Bifulco]

Hi,

If you want hierarchical Persistence you could use IndexedDB API, but i have to tell you that only modern browsers support it. For limit storage size the spec doesn't specify anything, so i think it's a specific browser property defined and customizable with or without some tricks. However if you have to store a great amount of data on your client try to consider other technical ways to do it: Java applet, or native sanboxed and wrapped client sometimes it's the best way to combine a web app with a native client requirements. As ever a stop point to analyze your requirements could bring more support Than other technical analysis.

To view this discussion on the web visit https://groups.google.com/d/msg/gwteventservice/-/HaN6MmWOGl4J.
To post to this group, send email to gwteven...@googlegroups.com.
To unsubscribe from this group, send email to gwteventservi...@googlegroups.com.