I was about to answer, then I remembered Kevin having done that before: "You may want to save cookies, but we explicitly don't do it on purpose, because it's a big security vulnerability. You can never rely on cookies being available between page renders (on igoogle the domain changes every time you move a gadget on your page and on orkut the domain changes every month or so), and when gadgets are cajoled writing cookies will be disabled completely. Gadget developers are told to use setprefs for storing data (and with open social we'll have the infinitely more robust appdata to rely on). The parent site may store / read cookies to implement setprefs and appdata, but actual cookie interaction is intentionally not a part of the gadget spec for these reasons."
So, basically, the answer tot your question is that you shouldn't want to use cookies. On 1/31/08, Piotr Jaroszyński <[EMAIL PROTECTED]> wrote: > > Hello, > > I have already asked this question on the gadgets-api mailing list - [1], > but > I suppose here might be a better place. > > I am wondering whether adding an option to forward cookies from the > fetched > sites back to the gadgets would be something desirable? Where by forward I > mean just passing them along other content to the callback function if e.g > . > GET_COOKIES option was specified. Looking at the proxy code it doesn't > seem > hard to do. > > [1] - > > http://groups.google.com/group/Google-Gadgets-API/browse_thread/thread/b857a8ecd448c01 > > -- > Best Regards, > Piotr Jaroszyński >
