Archive of UserLand's first discussion group, started October 5, 1998.
Author: John Tokash Posted: 5/11/1999; 10:20:58 AM Topic: Update on My.UserLand.Com Msg #: 6012 (In response to 5961) Prev/Next: 6011 / 6013
Another option is to register the rss file under an ID or a NAME of some sort. What if the rss file moves to a new host and the old host is put out to pasture?
In combination, we could use the
tag in old rss files to point to the correct ID or NAME. The 'client'(my.netscape servers or my.userland servers) could update its own records when it encounters such a redirect. Once all your clients are updated, remove the old file.
Unfortunately, this means some central id server with authentication for 'owners' of an rss file. This would make submissions of rss files from people who don't own the rss file bad news. They would essentially lock out the actual owner on his own rss file.
Still another option to avoid the host change problem is for people to register their rss file at userland and have userland provide stub rss urls that
(or http:redirect) clients to the appropriate rss url on the owners servers. It has the authentication problem still, though.
I guess Dave is right. The only TRUE way to get over the authentication hurdle is to have the owner of the file change the actual content of the file or change the webserver's behavior so that the original url actually points to a new one.
This page was archived on 6/13/2001; 4:50:01 PM.
© Copyright 1998-2001 UserLand Software, Inc.