reverse /atom/feed path args
samirnassar - December 5, 2007 - 17:42
| Project: | Atom |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
The default path to an Atom feeds is redundant: http://example.com/atom/feed. http://exmple.com/atom is a feed therefore atom/feed is just re-emphasis. I would suggest sticking with plain http://example.com/atom or perhaps the more expandable http://example.com/feed/atom where the path connotes that there is a feed of type atom. This could be expanded to http://example.com/feed/rss or other feeds if they come up.
#1
You get a feed when you go to just /atom (you shouldn't)? I think the general idea behind atom/feed is so future functionality could be perhaps /atom/newfeature. Moreover atom by itself could easily collide with a URL alias of atom with it just being a singular path (if for example pathauto was turned on and someone wrote a title named Atom).
Perhaps to fill this request, atom should reserve an alias for itself on install? What is the alternative if there is already an alias for atom?
I really lost you when you mentioned /feed/rss since the Drupal defaults are rss.xml and /path/path/feed, neither of which are feed/rss.
#2
Currently atom.module just appends /atom/feed to whatever it supports (site, node, term). And no, just going to /atom does not work out of the box.
The reason I find /feed/atom to be better than /atom/feed is that /atom already means that it is a feed. This is especially true in the combination /atom/feed. /feed/atom is preferable because feed is a more encompassing term then atom is. It also allows future feed modules to use the same namespace (if that is a term I can use).
In terms of doing things like /atom/newest this can still be done in /feed/atom/newest.
With regards to RSS feeds, I only brought them up as an example that they could be improved as well. With a structure like /feed/atom an improved rss.module (hypothetical) could share the /feed namespace and tack on /rss to becomes /feed/rss thereby allowing a drupal instance to advertise /feed/atom and /feed/rss for URI consistency.
#3
Existing functionality in core says /blog/feed is a legit RSS location, so then should /blog/feed/atom be considered breakage of that? I guess I'm wresting with the fact that /feed in Drupal by default means RSS, and there is no /feed/rss. So then might users think /feed/atom changes /feed?
Note, I'm not disagreeing with this request. I'm just trying to lay a clear path of logic before changing existing paths that would break feed readers of subscribers. Atom is a really old module and I know there's been a debate about this in the past - I just haven't found it.
#4
I'm going to switch to atom.xml.