I made the following comment in response to a post by Karsten Januszewski of Microsoft on the recently formed Aggregators mailing list:
With all due respect to Microsoft and in the spirit of feedback, the recent post suggesting RSS feeds be registered and discovered in UDDI and associated paper puzzles me. Why would I want to discover a simple lightweight syndication mechanism (RSS) through a mechanism that is significantly more complex and heavyweight as UDDI? Otherwise, from a technical perspective and at risk of sounding like a REST advocate, why would I want to discover a"service" that I retrieve with a simple HTTP GET with SOAP API calls? There are a number of mechanisms already deployed that allow one to register and discover feeds in a more lightweight fashion. How does this make the architecture more sustainable when UDDI is a centralized service and that does not have any type of push or pubsub mechanisms built?
I am of the opinion that while it may be "a logical application of UDDI in its mission" it defeats the mission of RSS.
Leave a comment