Re: [orbitcpp-list] iiop example wanted

[Michael R. <mi...@ru...>]

Hi,

your problem is known under the term bootstrapping in distributed systems.

I have a description of the problem on http://orbit-resource.sourceforge.net/faq.html

Michi Henning has a much more elaborate discussion here:

http://www.ooc.com.au/staff/michi/binding.txt

Hope this helps,

Michael

David Walter wrote:
> 
> Hi.  I am just starting to work with corba. I am using orbitcpp 0.28.1
> (current source version on the web with a debian woody installation of
> orbit.)
> 
> The application I am working on requires communication between
> different machines over the Internet.  My understanding is that in
> order to create the connection between the client and the server iiop
> is the natural method.
> 
> I  am not clear from the  material that I have   read either michi and
> steve's  book  or omg  docs  whether there  is a  local requirement to
> connect to a name server which  provides the service of "directing the
> connection from the local host to the  remote name server or orb" then
> to the remote server,  or  if there is   a standardized protocol   for
> dynamically requesting and establishing a connection.
> 
> I am guessing that there  is a step missing in  the model I understand
> so far, unless  iiop  invisibly handles the  underlying  socket/server
> communication and connection. Below is a generic understanding of what
> I think is happening for  a message to be  passed from a client to the
> server.
> 
> I am missing an  understanding of how the  initial ior is found by the
> client.  That is how  does the client establish  the connection to the
> remote server?  Does  the server publish  itself to a name  server via
> it's local name server(called remote in the diagram below), which then
> maintains  a permanent published   address at a  port  for  iiop based
> `consumer' clients to find?
> 
>                  [iiop methods]                    [server]
>                  +-----------+                        ^
>                  |           |                        |
> [client] -> [local orb]  [remote name server] -> [remote orb]
> 
> So I guess the questions that I have are:
> 
> 1. Who is responsible for providing the initial connection information
> from a client to a server over the internet?
>         a. name servers
> 
>         b. another middleware application which is done on an as
>         needed basis
> 
>         c. iiop calls which (either through name-servers or each
>         systems local orbs manages the connections transparently)
> 
> What  I would like is a  simple example  which demonstrates creating a
> connection to  a   remote  host (like echo-*   for   iiop) and  allows
> bidirectional communication between systems.
> 
> Is there a working example either in C++ or in  C which can be used to
> `grok the source   luke' or if  there  is documentation  which details
> this, I have missed it, my apologies, and pointers welcome.
> 
> (I  could cross post to comp.*corba  as well but  wonder if in general
> they will know any issues related to orbit* features in development --
> so I ask here. apologies if this is inappropriate.)
> 
> Thanks so much for any advice / pointers.
> 
> David
> _______________________________________________
> orbitcpp-list mailing list
> orb...@li...
> http://lists.sourceforge.net/mailman/listinfo/orbitcpp-list