Concept Clarification : Registering Client on Different Port
From: Phil Jones (phil_newsgroup_at_hotmail.com)
Date: 08/08/04
- Next message: Phil Jones: "Client/Server Interaction - works fine on one PC, but on two PC's it dies"
- Previous message: Phil Jones: "Your Event Wrapper - Thanks"
- Next in thread: Sam Santiago: "Re: Concept Clarification : Registering Client on Different Port"
- Reply: Sam Santiago: "Re: Concept Clarification : Registering Client on Different Port"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 8 Aug 2004 16:01:48 +1200
After doing battle with remoting events, and working through Sunny's "Event
Wrapper" sample I pretty much found the thing which was causing me grief.
That is - the server's channel is registered on one port, and the client
registers a channel on a different port. If this doesn't happen I get one
of these errors:
<<This remoting proxy has no channel sink which means either the server has
no registered server channels that are listening, or this application has no
suitable client channel to talk to the server.>>
I don't understand this. Why don't they use the same port? If the channel
has some other port, how does it know to talk to the server (I suppose
becuase the remote proxy object it's working with contains the actual server
port details from it's creation).
Anyhow, is this just something ya supposed to know - or is there a deeper
concept I should be grasping.
Cheers everyone!
===
Phil
(Auckland | Aotearoa)
- Next message: Phil Jones: "Client/Server Interaction - works fine on one PC, but on two PC's it dies"
- Previous message: Phil Jones: "Your Event Wrapper - Thanks"
- Next in thread: Sam Santiago: "Re: Concept Clarification : Registering Client on Different Port"
- Reply: Sam Santiago: "Re: Concept Clarification : Registering Client on Different Port"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
