Feed Handling/Handlers: Difference between revisions
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
As for web handlers, we will want to store a list somewhere, and expose a web API that allows a website to register itself as an alternative. This should be either through a script call or a <link> tag. | As for web handlers, we will want to store a list somewhere, and expose a web API that allows a website to register itself as an alternative. This should be either through a script call or a <link> tag. | ||
Discussion: | Discussion: [http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/ca4504a17217fc86/a5beb4d0f3498e17 mozilla.dev.platform] | ||
Latest revision as of 20:29, 12 April 2006
Handlers
There are three types of handler:
- native client application handlers (e.g. Mozilla Thunderbird)
- web handlers (Bloglines, Google Reader, etc)
- Firefox Live Bookmarks
Picking a Default
When we show the Subscribe view, it is important to select a good default handler, since feeds may or may not be a new concept to the user.
There are possibly heuristics here but I'm not yet sure what they are. Ideas welcome. In the interim we can probably pick the first one.
Registering Handlers
We can show the default client handler on the system for handling various feed types or the feed protocol.
As for web handlers, we will want to store a list somewhere, and expose a web API that allows a website to register itself as an alternative. This should be either through a script call or a <link> tag.
Discussion: mozilla.dev.platform