[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Publish and subscribe over the Internet
- From: Dave Winer <email@example.com>
- To: "XML-Dev (E-mail)" <firstname.lastname@example.org>
- Date: Tue, 16 Jan 2001 10:14:40 -0800
I sent Tim a private email that I should have sent to the list, it should be
on the record.
Imho, there are several components that are needed.
1. A registration point where anyone can declare "I want to subscribe to
this resource," identified by a URL.
2. The owner of the URL can query the registration point to find out who's
3. When the resource changes a message is sent to each subscriber, telling
it to invalidate its cache. The subscriber reloads the resource on the next
access and caches the result.
1. Registrations expire after 24 hours. This helps assure all participants
that you're alive and well.
2. The whole thing can be done with any of the following: SOAP, XML-RPC or
3. Subscribers should reload after some arbitrary amount of time even if
they haven't received notification from the registration point.
4. RSS makes good glue.
5. A lot of the functionality can be encapsulated in an FTP server or other
app that processes incoming stuff.
I've been working on servers and affiliates like this for 2+ years, and
keeping the various machines working has been a rich learning experience.
We're developing a new, much more broadly distributed and easy to use
network around these ideas, and have gone to the trouble of writing specs
and use-cases. Please, before reinventing what we already have working,
consider using it.
Dave Winer, UserLand Software
Daily notes: http://www.scripting.com/
"It's even worse than it appears."