http://weblogs.asp.net/tmarman/archive/2003/04/01/4639.aspxIn 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 thatenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/tmarman/archive/2003/04/01/4639.aspx#12381Tue, 01 Apr 2003 22:50:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:12381Tim MarmanTim MarmanRemoting 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?<img src="http://weblogs.asp.net/aggbug.aspx?PostID=12381" width="1" height="1">http://weblogs.asp.net/tmarman/archive/2003/04/01/4639.aspx#12379Tue, 01 Apr 2003 22:10:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:12379David StoneDavid StoneWhen you say: &quot;WebService&quot;, 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). <img src="http://weblogs.asp.net/aggbug.aspx?PostID=12379" width="1" height="1">