My Dream Aggregator

In response to my previous post on aggregators, David commented:

Sounds like what you need is a client/server Remoting based aggregator set. Where you have a server running at home that downloads all the feeds, and then you have multiple clients that just grab the stuff.

Exactly. What I kind of had in mind was something that runs and collects whatever feeds I'm subscribed to. My first inclination would be a Windows Service, but since I most likely couldn't install this on my web host, I'd have to run my home PC all day, but whatever.

Regardless - this server, wherever it is, would expose these feeds (and any associated updates, such as marking a post as read or flagging it for follow-up) via a web service. The various clients would simply talk back to this service.

You know, I'm starting to get fired up about this. When I finish my other side project, maybe I'll actually work on this! It might not be overly useful to other people, but it would definitely simplify my life just a bit....

And to David and DataGrid Girl (and all others reading this) - thanks for reading! :)

Published Tuesday, April 01, 2003 8:49 PM by Tim Marman
Filed under:

Comments

# re: My Dream Aggregator

Tuesday, April 01, 2003 6:10 PM by David Stone
When you say: "WebService", I'm assuming you really mean Remoting. You really don't need cross platform interop here (which is what SOAP/XML Webservices would give you). I'd thought about just keeping it in the family(.NET).

# re: My Dream Aggregator

Tuesday, April 01, 2003 6:50 PM by Tim Marman
Remoting is fine, but why limit the aggregator only .NET consumers? I don't know too much about remoting though - what channels is it typically done over? And if I can do it over HTTP, how does that differ from a WebService?

Leave a Comment

(required) 
(required) 
(optional)
(required)