Does this sound like LLUP or what!?
Great minds and all that... well, I might not have a great mind but Michael Sparks certainly seems to have.
Not only is his blog one of the most entertaining reads I've had the pleasure to come across in a long time, but this entry in particular piqued my friend Sylvain's interest. Mostly because we share the view on how the current RSS as pipe view on the world is faulty, but also because we, along with M. David Peterson, have been working on something that aims to hit those flaws on the head.
LLUP[1] anyone?
[1] The LLUP System in a nutshell
LLUP stands for Limited Lifetime Ubiquitous Protocol. What it does is simply allow you to subscribe to particular types of content (on criteria such as geographic area of interest or other simple keywords) and then for content producers to notify your account when something of interest has been made available. Think of it as a system somewhere between email (push) and web sites (pull). A content producer puts out some content and then sends a notification, called a blip, into the LLUP system. The LLUP system the smartly propagates the blip to anyone who has expressed an interest. A presentation overview of the LLUP system is available here.
To do this, LLUP is made up of three services that are all defined using open standards. The Publication service provides an interface where content creators and producers can tell the system that new content is available and what it is relevant to (and also to ensure that only known sources can send into the LLUP system, overcoming some of the issues with spam*). The Subscription service allows content consumers to subscribe to different types of blip. The BlogXast service is a combination of a publication service and the subscription service in that it provides a smart router that can route blips intelligently throughout a system.
Although different implementations of the LLUP services are possible, web services are the most common and so that is what we have implemented with Rails here.
* In terms of authentication, LLUP is moving forward into using SAML to handle federated user account information and this is a significant step towards protecting LLUP from some of the same issues that plague email.
References (17)
-
Response: ParkerBraedon -
Response: JadeDarrel -
Response: JoeyBrandyn -
Response: BernardLeslie -
Response: JaimeMonte -
Response: DarionKobe -
Response: KelseyDeandre -
Response: JeanCarson -
Response: AryanStephan -
Response: AryanStephan -
Response: MarcusElliott -
Response: RonnieTeddy -
Response: Phentermine 37.5 mg.Phentermine 37.5 mg online prescription. 37.5 mg phentermine overnight delivery. -
Response: Soma online sales.Soma online sales. Buy soma online. -
Response: Phentermine online.Phentermine online. Purchase phentermine online. Phentermine online consultation. Can i order phentermine online. Cheapest phentermine online. Online phentermine. -
Response: a3ab7751facade032e45a3ab7751faca -
Response: Generic phentermine.Phentermine generic 37.5 free consultation. Adipex generic form phentermine lowest prices. Generic phentermine. Buy generic phentermine bloghoster.







Reader Comments (2)
SWEET!!! :D
Back from Seattle now... ping me when you're around :D
I found this idea of publish and subscribe interesting as an alternative to email, in particular the filtering and idea of subscribing to content :
"messages are targeted to only those end points that have expressed an interest so that services don't receive messages when they are not required or interesting"
One of the advantages of this is it avoids spam, however the reason email is open is to allow a channel for unknown others to get in touch. Your proposed alternative (not just to email but to other submission data) offers no variety of 'push'.
Also it's obviously dependent on tools and widespread use. Do you have any plans to try to produce an example implementation in some commonly used language, lik,e c, python or ruby?
Since I'm here, just thought you'd like to know that your site at
http://dev.llup.org/
has been overrun by spam. If you're not using it anymore perhaps it'd be worth shutting it down and putting up a link to your new site? I followed a link from Oreilly to the old one and it looks dead.
There are a few mistakes of grammar and spelling in your RFC on your new site which it might be worth correcting. e.g. :
is not computer's litterate
should be
are not computer literate
There are a few more, along with the consistent misuse of apostrophes for plurals (e.g. 'BLIP's' )