Re: Question on Client - Server communication

[john.nospam@nospamassen.nospamdemon.co.uk (John McCabe)]

On Fri, 5 Jul 2002 10:08:18 +0200, Preben Randhol
<randhol+ada@pvv.org> wrote:

What you seem to want is something like an Object Resource Broker.
It's probably worth looking at some CORBA documentation to see if it
gives you any ideas.

I did something similar a couple of years ago. This involved what I
called a Resolver - a client would ask the resolver for information on
which port to connect a service on. The resolver would provide this
information. The Resolver would always on the client's local machine.
Servers would register themselves with the Resolver, also on their
local machine. There would be 2 different types of resolver, but
clients and servers would not be aware of this. One type of resolver
would maintain the database of services (and allocate port numbers as
required), and would be queried by the other type of resolver when it
needed some information, so the resolver was always on a known port.
Where the information came from (i.e. the local resolver or the remote
resolver after a query by the local resolver) would be completely
transparent to any clients or servers that were running.

From what I can tell this was a huge simplification of what goes on if
you use CORBA, but worked for what we needed at the time.

How you do the communication between your clients/servers and their
local resolver is pretty much up to you.

Hope this is of use.