Thanks for the replies. Eventually I used the web storage solution defined by HTML 5 drafts and supported by most browsers today in what seems to be a fairly reliable way.
Here's some sample code: http://code.google.com/p/visitingcardgadget/ On Jan 15, 9:34 am, Avital Oliver <[email protected]> wrote: > It seems that lately the domain of the iframe containing gadgets of the same > URL are also the same (some hash of the URL I assume). This means that you > can use various methods of local storage (for example by > usinghttp://pablotron.org/?cid=1557) and all instances of your gadget will > have > access to the same data. You don't need HTML5 if you're storing small > amounts of data - all browsers support cookies (that can be accessed from > javascript -http://www.quirksmode.org/js/cookies.html) for local storage. > > Not sure if this hashed gadget URL will stay, but we've been using this to > set our gadget to "debug" mode across all instances and it is working for > us. > > Avital. > > --http://wave.theWE.nethttp://twitter.com/theWE_ > > On Fri, Jan 15, 2010 at 8:50 AM, Eyal <[email protected]> wrote: > > I want to develop a gadget that stores persistent data for each user: > > When a user inserts the gadget for the first time, the gadget asks for > > some information. However, when the user adds the gadget again, that > > gadget will already have access to that information. That is, the data > > should be persistent but not shared, across all rendering requests and > > creation requests. > > > I was thinking of some ways to implement this: > > > 1. Using a remote server to store the data for each user and a browser > > cookie to fetch it. > > 2. Using HTML 5 or Google Gears to store the data locally. > > 3. Using opensocial - Since Wave gadgets use the opensocial container, > > I thought that it might be possible to use the opensocial API to store > > application data for the viewer (specifically by using > > newUpdatePersonAppDataRequest()). Unsurprisingly, the opensocial RPC > > returns error 401: UNAUTHORIZED. > > > Any other ideas? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Wave API" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-wave-api%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en.
-- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
