On Wed, Feb 27, 2008 at 10:28 PM, Sean McCarthy <[EMAIL PROTECTED]> wrote:
> Hi all, > > After a possibly not-so-thorough reading through of the gadget API, > the shindig source and the shindig-dev list archives I can't > determine if there's > > 1. A specification/API for the persistence of UserPrefs to a store Up to the container. Every container has their own way of storing data -- you register your own set_pref rpc handler and do whatever you like beyond that. Some sites might store this to a mysql server, others might store it in cookies. 2. Any intent to create a persistent store other than the > CookieBasedUserPrefStore implementation already in shindig If / when we have an appdata implementation, we'll probably wire that up, but even then it'll just be a dummy file based mechanism. This is highly dependent on your own site's infrastructure. There's no way for shindig to be able to decide what's "right". > > > So, I guess my question is can anyone enlighten on the above? > > If there aren't any specific plans to create a non-cookie persistence > mechanism then I can happily attempt it myself, but if doing so I'd > like to make sure I was following a specification (i.e. some RESTful > service API?) if it existed. The specification here is the set_pref handler of gadgets.rpc. Beyond that, it's all in the hands of the container.
