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
> My understanding is that "Remoting" is more involved and requires setting up
> listeners.
[quoted text clipped - 3 lines]
> >
> > Can I build an rpc based web service with VS.NET.2003 ?
Elp - 05 Aug 2004 13:03 GMT
> 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.
But you can use SOAP formatters and specify the port to listen to on the
server side with Remoting so where is the problem? You can even use an HTTP
channel so this should work quite well (in theory) through NAT and
firewalls.
Jim Hubbard - 06 Aug 2004 01:43 GMT
http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&safe=off&edition=us&th
readm=v2jtr7qb695fee%40corp.supernews.com&rnum=1&prev=/groups%3Fnum%3D100%26hl%3
Den%26lr%3Dlang_en%26ie%3DUTF-8%26safe%3Doff%26edition%3Dus%26q%3Dremoting%2B%25
22jim%2Bhubbard%2522
> > Although Remoting excited me when I first heard of it, I quickly lost
> > interest when I realized the extremely limited usefulness of the
[quoted text clipped - 4 lines]
> channel so this should work quite well (in theory) through NAT and
> firewalls.