Confirmed users, Bureaucrats and Sysops emeriti
3,599
edits
2005Offiste/RSS Integration: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
= Ben's architectural diagram = | |||
.---. .----------------. | .---. .----------------. | ||
| Line 7: | Line 6: | ||
.---------. | .---------. | ||
.--------. |Protocol | | .--------. |Protocol | .----------. | ||
| feed : | ---------> |Handling | | | feed : | ---------> |Handling | | Internal | pretty printing? | ||
'--------' '---------' | '--------' '---------' /| Handlers | ---> web services? | ||
| | | / | | preview? | ||
.---------------. V | .---------------. V / '----------' | ||
| Content Types | .---------. / .----. | | Content Types | .---------. / .----. | ||
| app/rss+xml | --> | UCT |-- | | app/rss+xml | --> | UCT |-- | | | ||
| app/atom+xml | | System | \--| OS | ---> system registered reader | | app/atom+xml | | System | \---| OS | ---> system registered reader | ||
'---------------' | | | '---------------' | | | | | ||
'---------' | '---------' '----' | ||
= Discussion = | |||
* beng, chofmann: RSS is just another type of web content, and we should try to provide a transient experience where we display that content in the most appropriate fashion | * beng, chofmann: RSS is just another type of web content, and we should try to provide a transient experience where we display that content in the most appropriate fashion | ||
| Line 26: | Line 27: | ||
* beng: part of this requires us to have a better UCT system UI which provides a better user experience for dealing with a file of unknown content type | * beng: part of this requires us to have a better UCT system UI which provides a better user experience for dealing with a file of unknown content type | ||
** uses OS hooks and a WSDL service to detect and suggest handlers | ** uses OS hooks and a WSDL service to detect and suggest handlers | ||
** this UI and the UI for registered content type handers needs to be revisited and revised, most likely | |||
* beng: better integration with [[Places|the places work]] might solve some of these problems, too, as it will allow for easier searching, archiving, marking read/unread, etc. | * beng: better integration with [[Places|the places work]] might solve some of these problems, too, as it will allow for easier searching, archiving, marking read/unread, etc. | ||
** dveditz: could be also used to show the last visited date | |||
* what about future uses of the RSS/Atom formats (ie: podcasting) that we can't predict? | |||
* sgarrity: right now Firefox offers no support for grabbing the RSS feed off a page and handing it off to my feed reading application | |||
** beng: I think ultimately that needs to go through the protocol handlers of UCT system (see diagram above); we can also leverage some of the RSS detection code that we backed out | |||
** sgarrity: Safari currently obeys the system registered RSS reader, even in the "RSS" button | |||
** beltzner: the danger there is that it doesn't allow for someone to create a LiveBookmark | |||
** beng: right now in prefs we show an elaborate dialog that illustrates registered content handlers, this is where I'd suggest we do that. The [x] Always Use this handler button might be a solution here. Or alternatively to have an "Open With ..." metaphor. | |||