You are right. Remoting does require setting up listener programs on ports
specified by the developer.
RPC is of most use internally, because remoting does not work for machines
behind NATed firewalls.
RPC also uses a binary protocol which is much lighter and faster than HTTP
protocol.
This introduces another problem if you are thinking of using Remoting for
general use from a web page. Most firewalls block anything that is not FTP
or HTTP traffic - that includes RPC protocols.
Although Remoting excited me when I first heard of it, I quickly lost
interest when I realized the extremely limited usefulness of the technology
due to NATs and firewalls.
Another almost-got-it-right moment for Microsoft.
Jim Hubbard
"Scott M." <s-***@nospam.nospam> wrote in message
news:el****************@TK2MSFTNGP10.phx.gbl...
My understanding is that "Remoting" is more involved and requires setting
up listeners.
"Delmar de Frasi" <dd*****@yahoo.com> wrote in message
news:an****************@newsread2.news.pas.earthli nk.net... What are the differences between a http web service and a rpc web
service ?
Can I build an rpc based web service with VS.NET.2003 ?