Hey Matt,

I would maybe suggest trying the AJAX Feed API over the gadgets one.

http://code.google.com/apis/ajaxfeeds/documentation/reference.html#JSON

I personally find it way more stable and reliable then the gadgets
version (IMHO). Plus they also have RESTful aspects (probably best for
gadgets and less code needed) and can include the XML string also
(&output=json/json_xml/xml)

http://code.google.com/apis/ajaxfeeds/documentation/reference.html#_intro_fonje

I have been using it a lot and am very happy with its stability, but
maybe that's just me, you can try it and decide for yourself. :)

Just a quick snoop at the first link;

author
The feed author. Corresponds to the <name> element for the author in
Atom.

So maybe try using the ATOM feed for groups over the RSS if its a
problem.

Also, I know the first link does not show the author for the entries,
but the RESTful data (raw JSON) does. (#_intro_fonje), Worst case
scenario the XML string will give you all the data (&output=json_xml/
xml).

But, you can check out this link below to see the author data in JSON
format (,"author":"Matt (Guru)",)

http://ajax.googleapis.com/ajax/services/feed/load?v=1.0&q=http%3A%2F%2Fgroups.google.com%2Fgroup%2FGoogle-Gadgets-API%2Ffeed%2Fatom_v1_0_msgs.xml

Hope that helps,
Vision Jinx

On Apr 29, 2:35 pm, "Matt (Guru)" <[email protected]> wrote:
> I've been frustrated many times that _IG_FetchFeedAsJSON doesn't read
> the <author> tag and put it into the JSON.
> Is there any good reason for this? Could it be enhanced to populate
> this field as well?
> It's especially useful when getting RSS feeds from Google Groups.
>
> Matt Kruse
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to