To be clear, I'm opposed to using the browser's cookie jar and, by extension, the rendering domain scheme to store cookies. With another storage mechanism defined, I'm open to discussion. --John
On Thu, Feb 26, 2009 at 2:36 PM, John Hjelmstad <[email protected]> wrote: > To be clear, by browser-passed and "proxy" you mean that makeRequest become > a mechanism for setting cookies (and sending) on the domain on which a > gadget is rendered? > --John > > On Thu, Feb 26, 2009 at 2:28 PM, Jordan Zimmerman <[email protected]>wrote: > >> >Subscribe to the opensocial-and-gadgets-spec and read through some of >> >the archives for OpenSocial 0.9 spec proposals: >> >http://groups.google.com/group/opensocial-and-gadgets-spec. >> Thanks. Unless you object, I'd like to propose something different - >> that makeRequest proxy cookies. It would be straightforward. The >> container includes any browser-passed cookies to the target URL and the >> container returns any set-cookie headers in the response back to the >> browser. >> >> 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. >> > >
