Hi, I started implementing a container using shindig as my gadget server and I have a few questions regarding the way shindig gets and caches the gadget XML.
First, I'd like to know what's considered the best practice for the expiration time of cached gadgets? Does it have to be in some kind of range for my container to be spec compliant? Secondly, does shindig cache the gadgets only on the machine's memory, or does it also support using a distributed cache? If i set a very long time for my container to update the gadget XML (and perhaps allow the developer "update me" functionality), would it be reasonable to save it on my database (maybe save it already parsed)? Also if i keep an "Application Directory" of approved apps that i allow on my container, is it really necessary to send the gadget XML URL to when sending a gadget rendering request? If i implement my own gadget server, could i simply send an application Id (managed by my site) and on the server side get the appropriate URL for that application (or even the XML itself from the cache)? I'm asking these questions because i think I'm missing something. I would like to minimize the amount of times my servers have to parse the gadget xml. Saving the gadget spec already parsed would allow me to do that. Thanks in advance, Eran
