Re: is there a way for a client to detect a server on the network
From: M.Posseth (michelp_at_nohausystems.nl)
Date: 12/29/04
- Next message: Ming: "dependency problem in .NET Remoting"
- Previous message: Fernando Cardoso: "Re: customErrors"
- In reply to: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Next in thread: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Reply: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 29 Dec 2004 13:08:20 +0100
Well this pointed me in the right direction
i will investigate IP broadcast / multicast
and see if i get something working ,,,,
do you know of some good references on the web that might help me in my task
??
-- Met vriendelijke groet Kind regards, Michel Posseth Software Developer Microsoft Certified Professional "Arnaud Debaene" <adebaene@club-internet.fr> wrote in message news:OAGUHQZ7EHA.1264@TK2MSFTNGP12.phx.gbl... > M. Posseth wrote: > > Hi ,,, > Hello. > > > > So my client server proggy works as it should be ,,, however it would > > be nice if i could find a way that a starting client could do a > > broadcast over the network to discover availlable servers and the > > user could then select the server he prefers . > .NET remoting does not provide service discovery nor service dictionary, so > you need to do it yourself. > > > This would solve a lot of potential problems ,,i already thought > > about sending a normall call to all availlable ip adresses on the > > network however this would take hours as it is far to slow > Ever heard about IP broadcast or (better) multicast ? > > > does anyone have an idea how to acomplish this with TCP remoting or > > with alternatively sockets ??? > Remoting won't be of any help here Yo need to build yourself a protocol on > top of TCP sockets (or more probably UDP since it's best suited for > multicast/broadcast scenarios). > This would probably means that each server would listen on another port (not > 8080, another one) for a multicast "search" request. It would answer to > these requests by a frame where it gives the address (probably the URI) of > the available remoting object. > Of course others architectures could be used, such as a central, > known-from-everybody, dictionary service where servers register themselves > when they start up, and client can interrogate this dictionary to find > needed servers URIs. > > Arnaud > MVP - VC > >
- Next message: Ming: "dependency problem in .NET Remoting"
- Previous message: Fernando Cardoso: "Re: customErrors"
- In reply to: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Next in thread: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Reply: Arnaud Debaene: "Re: is there a way for a client to detect a server on the network"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading