"Ralph" < XXXX@XXXXX.COM > schrieb im Newsbeitrag
Yes, other than DCOM (wich works over a huge Range of Ports),
our Implementation works/listens on a single Port only.
If you open your serverside firewall for this RPCServer-Port,
then all should work flawlessly.
The Default-Port is 22222, but you can set any Port you want in the
To avoid problems with clientside Firewalls, wich sometimes are
configured to block "unknown Ports" even for outgoing connections,
you can set the RPCServers Port to e.g. 80 (the http-defaultport).
This way you can avoid those potential clientside firewall-problems
(of course the RPC-Host shouldn't run a Webserver, listening on Port 80
at the same IP then).
Our underlying protocol is not http-based, but the server can answer
http-requests with a simple Status-Message - so there's no problem
that the server will crash with "unknown protocol", due to eventually
incoming http-requests over Port 80 from "normal WebBrowser-Clients".
You can check the http-responsibility of our running server (currently
listening on the Default-Port 22222) with your Browser entering