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]. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
