Thanks for the response - shame it can't just be taken from iGoogle! I had thought the Shindig solution would also be server-side, but for a temporary solution you raise a good point that a client-side library could do the trick, although feed parsers I've used in PHP tend to be large, so it would be a waste to download even when not used.
Perhaps I'll see if I can work out a quick fix at some stage, but unfortunately can't even look at it for a while, so don't let my comments here prevent anyone else from also trying to build a solution... -----Original Message----- From: Kevin Brown [mailto:[EMAIL PROTECTED] Sent: 28 March 2008 18:26 To: [email protected] Subject: Re: Support for ContentType.FEED in makeRequest On Fri, Mar 28, 2008 at 5:39 AM, Dan Lester <[EMAIL PROTECTED]> wrote: > > I've found JIRA 60 which says "Shindig does not properly support the > FEED content type as defined by the gadgets spec for > gadgets.io.MakeRequest" and it is currently unassigned. > > I'm coming across a number of gadgets that are trying to use this > feature - it's certainly a lot easier than parsing an XML feed; in > gmodules there is server-side code to break up the actual RSS fields > into a JSON structure. > > Anyway, it occurred to me that this code must already exist somewhere > within Google... Would it be possible to at least commit (or post > elsewhere) the basic code to do that, even if it is not yet fully > integrated into Shindig? There are many RSS & Atom parsers out there -- we've been sort of punting on this until we get Abdera integration (which will come in the next few weeks with the RESTful API project). Are you looking for a solution in javascript, or a server side solution? Currently igoogle (gmodules.com) uses a server side solution for parsing feeds, and I can definitively say that it's not something that can be contributed to Shindig due to fundamental architectural differences, having worked on igoogle myself. I think we'd definitely welcome someone contributing a solution, even if it's only a temporary one. > > I can't promise to be able to take the steps required to integrate it > with Shindig, but some other general member of the public (or me) > might be able to help from there, if the 'offical' coders aren't able > to address it. Certainly, it does not make sense to start from > scratch, assuming Google are still able to be generous with their > existing code. > > Thanks, > > Dan > > -- ~Kevin
