Re: Callbacks to remoced clients thru firewall
From: Elp (rockfamily_at_REMOVEME.hotmail.com)
Date: 03/05/04
- Next message: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Previous message: Allen Anderson: "Re: UnauthorizedAccessException"
- In reply to: Isaak: "Callbacks to remoced clients thru firewall"
- Next in thread: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Reply: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 17:55:22 -0000
Hi Isaak,
"Isaak" <anonymous@discussions.microsoft.com> wrote in message
news:B55ACDB6-356E-4649-BA5B-D1E1D24DDBDE@microsoft.com...
> In my application, remoted clients, using auto port selection option of
port=0, register for remote callbacks from the server.
> Since port number is picked by the system, I have no control of which port
number is selected. My problem is that our server will soon be placed
behind the firewall, and with that >only certain preassigned port numbers
will be available for both inbound and outbound communications. Because I
may want to run multiple copies of remoted client from the same >machine at
the same time, I can't hardcode the port number into the client. Is there a
way to specify a range of "valid" port numbers for a client to choose form?
And if not, is there >another approach that will allow to have multiple
remoted clients running on the same node to receive callbacks from a server
when a pool of available port numbers is restricted?
An alternative as Sunny's approach would be to use a bi-directionnal channel
such as the one provided by Genuine Channels: http://www.genuinechannels.com
With this kind of channels, the channel that your client application uses to
connect to the server is re-used by the server whenever he needs to call a
callback function on the client (or send an event to the clients which is
actually the same thing). In this way, all you will have to do is to
configure your firewall to allow connections from wherever to your server
machine on the port used by the server to expose your remoting objects.
Exactly as if there was no callbacks or events involved...
- Next message: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Previous message: Allen Anderson: "Re: UnauthorizedAccessException"
- In reply to: Isaak: "Callbacks to remoced clients thru firewall"
- Next in thread: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Reply: Sunny: "Re: Callbacks to remoced clients thru firewall"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|