From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3190aba277f0ce3e X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-07-05 03:08:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!kibo.news.demon.net!news.demon.co.uk!demon!pipehawk.demon.co.uk!not-for-mail From: john.nospam@nospamassen.nospamdemon.co.uk (John McCabe) Newsgroups: comp.lang.ada Subject: Re: Question on Client - Server communication Date: Fri, 05 Jul 2002 10:09:38 GMT Message-ID: <3d256e38.6304224@news.demon.co.uk> References: NNTP-Posting-Host: pipehawk.demon.co.uk X-NNTP-Posting-Host: pipehawk.demon.co.uk:158.152.226.81 X-Trace: news.demon.co.uk 1025863631 nnrp-01:24262 NO-IDENT pipehawk.demon.co.uk:158.152.226.81 X-Complaints-To: abuse@demon.net X-Newsreader: Forte Free Agent 1.21/32.243 Xref: archiver1.google.com comp.lang.ada:26870 Date: 2002-07-05T10:09:38+00:00 List-Id: On Fri, 5 Jul 2002 10:08:18 +0200, Preben Randhol 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.