That's a very interesting point Piotr. What about a special type of UserPref that has the same interface as a cookie. The makeRequest would then treat that UserPref as the cookie data when communicating with the proxy (whether it puts the data in the request or not is an implementation detail). Then on the proxy, it would retrieve that data and use it as a real cookie on the external request. If the request result included changing the cookie, that data would be passed all the way back to the UserPref.
For sites that are dependent on cookies, this would make porting to a gadget much easier. I'm sure there are more issues, e.g. cost of uploading large cookies. On Jan 31, 2008 7:43 AM, Piotr Jaroszyński <[EMAIL PROTECTED]> wrote: > On Thursday 31 of January 2008 16:25:39 Reinoud Elhorst wrote: > > The problem is that the gadget is being loaded from (for instance) > > a.gmodules.com. This mean that any cookies that get set are set on > > a.gmodules.com. This is a restriction in the browser. The security issue > is > > here: > > (snip) > > I understand the problems with that, but that's not what I am proposing > here. > You are talking about gadget <-> user stuff and I am talking about gadget > <-> > proxy <-> 3rd-party site. What I want to be able to do is to fetch the > cookies sent by the 3rd-party site to the proxy and handle them in the > gadget, e.g. use for another fetch of the 3rd-party site. User's browser > wouldn't be involved in that at all. Think about the cookies as extra data > you get along the fetched content. > > -- > Best Regards, > Piotr Jaroszyński >
