On Thu, Feb 26, 2009 at 3:00 PM, Jordan Zimmerman <[email protected]> wrote: > However, I don't see any problems with the gadget setting/getting > cookies from its remote server. It's implicit in the spec anyway > (especially if your proposal were to be accepted > http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread > /thread/51b016b80e9d21e6?pli=1). Why not make this easier on gadgets?
Sounds like you are proposing a javascript library that implements browser cookie rules on top of makeRequest. I'd be fine with that, in principle. In practice It's hard to mimic the cookie jar precisely, some of the rules are subtle. Quick! What should happen if foo.example.com and bar.example.com set two cookies like this? foo.example.com: name=v1; path=/bar; domain=.example.com bar.example.com: name=v2; path=/bar/some; domain=.example.com Rather than worry about that question, I think we should get makeRequest to expose the cookies, then let other people build libraries on top of that functionality. Cheers, Brian
