You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Marshall Shi (JIRA)" <ji...@apache.org> on 2012/07/24 07:44:33 UTC
[jira] [Created] (SHINDIG-1825) Automatically recognize feed URLs
Marshall Shi created SHINDIG-1825:
-------------------------------------
Summary: Automatically recognize feed URLs
Key: SHINDIG-1825
URL: https://issues.apache.org/jira/browse/SHINDIG-1825
Project: Shindig
Issue Type: New Feature
Components: Java
Affects Versions: 3.0.0
Reporter: Marshall Shi
Sometimes a few "gadgets" are actually feeds, Shindig will throw exception when they find that "gadgets" are actually feeds. iGoogle recognizes this and substitutes a feed reader configured for the specified URI.
This feature will support using a specified feed reader gadget to substitute a feed rendering. The feed url will be placed into a variable in the feed reader gadget, render feed reader gadget instead of the feed itself. And feed reader gadget will fetch the feed according to the feed url in its onload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SHINDIG-1825) Automatically recognize feed URLs
Posted by "Rich Thompson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436781#comment-13436781 ]
Rich Thompson commented on SHINDIG-1825:
----------------------------------------
Seems there are several options for dealing with this use case:
1. Extend the gadget metadata parsing to recognize the additional format and substitute a configured gadget to render the feed (proposed in the description above)
2. New client-side code to define a new type of 'gadget sites' that knows how to render the feed
3. Leave it as an issue for individual containers to deal with
4. Change the metadata parsing to being a chain of parsers. The gadget metadata parser would fail on the feed URL and so the next in the chain would be given a shot at it. whether a parser that understood the feed format substituted a gadget or transformed the feed into html (is if it had been what came in from the feed URL) for rendering in a URL site was configured as the first in the chain to recognize the format would control how the processing flowed and the feed was rendered.
I prefer #4 as it not only deals with this use case, but also establishes an architected means for dealing with additional formats without creating more client-side code to download and run in the browser.
> Automatically recognize feed URLs
> ---------------------------------
>
> Key: SHINDIG-1825
> URL: https://issues.apache.org/jira/browse/SHINDIG-1825
> Project: Shindig
> Issue Type: New Feature
> Components: Java
> Affects Versions: 3.0.0
> Reporter: Marshall Shi
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Sometimes a few "gadgets" are actually feeds, Shindig will throw exception when they find that "gadgets" are actually feeds. iGoogle recognizes this and substitutes a feed reader configured for the specified URI.
> This feature will support using a specified feed reader gadget to substitute a feed rendering. The feed url will be placed into a variable in the feed reader gadget, render feed reader gadget instead of the feed itself. And feed reader gadget will fetch the feed according to the feed url in its onload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira