Good point. I'm OK with explicitly-passed cookies, just not using them implicitly during rendering. --John
On Thu, Feb 26, 2009 at 1:24 PM, Brian Eaton <[email protected]> wrote: > I sort of agree with John on this, but I'm not quite as much of a > cookie-hater as he is. Cookies in the browser cookie jar don't make > sense for gadgets. Cookies with gadgets.io.makeRequest, though, can > be useful. It has come in handy for integration of gadgets with > third-party web services that require cookies. > > I put together a spec proposal on this, and it is implemented in > Shindig. It's not a formal part of the opensocial spec, yet. > > > http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/51b016b80e9d21e6?pli=1 > > Jordan, if you believe this is the right approach would you be willing > to drive it through the opensocial spec process? > > Cheers, > Brian > > On Thu, Feb 26, 2009 at 1:15 PM, John Hjelmstad <[email protected]> wrote: > > No -- gadgets run on a jail domain for the obvious security reasons, > which > > is not stable from the perspective of the gadget developer (even a locked > > domain algorithm may change) and which may be shared by other gadgets > (more > > security issues). As such, cookies don't make sense for gadgets, so > proxying > > them would just add confusion. > > --John > > > > On Thu, Feb 26, 2009 at 1:10 PM, Jordan Zimmerman <[email protected]> > wrote: > > > >> Is it planned that makeRequest will eventually proxy cookies? Currently, > >> it doesn't. It would be easy to add to Shindig but if it's not part of > >> the spec gadgets can't count on it. > >> > >> Jordan Zimmerman > >> Principal Software Architect > >> 831.647.4712 > >> 831.214.2990 (cell) > >> [email protected] > >> > >> SHOP*COMTM > >> Shop Smart, Save Big(tm) > >> www.shop.com > >> > >> This message (including any attachments) is intended only for > >> the use of the individual or entity to which it is addressed and > >> may contain information that is non-public, proprietary, > >> privileged, confidential, and exempt from disclosure under > >> applicable law or may constitute as attorney work product. > >> If you are not the intended recipient, you are hereby notified > >> that any use, dissemination, distribution, or copying of this > >> communication is strictly prohibited. If you have received this > >> communication in error, notify us immediately by telephone and > >> (i) destroy this message if a facsimile or (ii) delete this > >> message > >> immediately if this is an electronic communication. > >> > >> Thank you. > >> > > >
