On Thursday 31 of January 2008 18:27:08 Brian Eaton wrote: > On Jan 31, 2008 7:43 AM, Piotr Jaroszyński <[EMAIL PROTECTED]> wrote: > > 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. > > I agree, it would be cool to have a way to do this. The HEADERS > parameter to makeRequest (currently unimplemented) might be where to > start.
Happy to hear that! Implementation of the HEADERs (it is cool for other reasons too and seems rather simple to do) in make_request is indeed necessary to handle the gadget -> proxy -> 3rd-party site part. I have actually managed to make it work with the old(current) gadget API by hacking with the internals of _IG_FetchContent a bit (the google proxy already has the support for extra headers). The other way around would need additional changes. btw. how close is the shindig project to how Google is doing things? Do changes made here have a good chance of being backported to the Google backend? -- Best Regards, Piotr Jaroszyński
