My view is that the container is acting as proxy for the request and proxies generally retain cookies. Not setting cookies has two potential problems. 1) Most servers allocate some kind of internal session for requests, so each makeRequest will end up allocating a new session which is wasteful. 2) Gadgets may want to make a sequence of makeRequest calls and having a session would make this far easier.
Of course, you could do it with URL parameters, but that's a pain and is why cookie-based sessions were developed to begin with. >Jordan, if you believe this is the right approach would you be willing >to drive it through the opensocial spec process? I'd be very interested! What do I need to do? 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.
