[omniORB] FW: Problem w/ Client/Server Communication Across L AN With Client /Server NameServices

Wed Oct 16 18:49:01 2002

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2753C.2EABE520
Content-Type: text/plain;
	charset="iso-8859-1"

OK I'm running 2.8 on Solaris 2.5.1. I start omniNames from an rc script as
follows:

	$OMNI_HOME/bin/omniNames -start 1234 -logdir $OMNI_LOG
>$OMNI_LOG/omniNames.log 2>&1 &

The difference between the IOR in the omniNames.log file and the one
produced with:

            genior IDL:omg.org/CosNaming/NamingContext:1.0 serverhost port#
NameService

is the end of the IOR which appears to be the object ID. If the IOR is
different every time omniNames is started
due to the object ID how is it possible to make omniNames have the same IOR?

Wayne Smith
wsmith@btg.com
410-286-9762

-----Original Message-----
From: bjorn rohde jensen [mailto:bjensen@fastmail.fm]
Sent: Tuesday, October 15, 2002 1:22 PM
To: Smith, Wayne
Cc: 'omniorb-list@omniorb-support.com'
Subject: Re: [omniORB] FW: Problem w/ Client/Server Communication Across
LAN With Client /Server NameServices

Hi Wayne,

  Yes, there is indeed a way to make omniNames have
the same IOR on a particular host, at least for
versions since 3.0.3. You need to start omniNames
on the same port and interface, which it ought to
do by itself, unless you are using dynamic IP's.
If you must use dynamic IP's, you could tell
omniORB to use hostnames instead, but then you
need static hostnames instead of IP's....
  The entries, you are refering to, in the config
file are used to configure the initial_references,
and omniNames does not use them for anything.

Yours sincerely,

Bjorn

------_=_NextPart_001_01C2753C.2EABE520
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [omniORB] FW: Problem w/ Client/Server Communication Across =
LAN With Client /Server NameServices</TITLE>
</HEAD>
<BODY>

OK I'm running 2.8 on Solaris 2.5.1. I start =
omniNames from an rc script as follows:

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>$OMNI_HOME/bin/omniNames -start 1234 -logdir $OMNI_LOG =
&gt;$OMNI_LOG/omniNames.log 2&gt;&amp;1 &amp;</FONT>
</P>

<P><FONT SIZE=3D2>The difference between the IOR in the omniNames.log =
file and the one produced with:</FONT>
</P>

<P><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; genior IDL:omg.org/CosNaming/NamingContext:1.0 serverhost port# =
NameService</FONT>
</P>

is the end of the IOR which appears to be the object =
ID. If the IOR is different every time omniNames is started
 due to the object ID how is it possible to make =
omniNames have the same IOR?

<P><FONT SIZE=3D2>Wayne Smith</FONT>
<BR><FONT SIZE=3D2>wsmith@btg.com</FONT>
<BR><FONT SIZE=3D2>410-286-9762</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: bjorn rohde jensen [<A =
HREF=3D"mailto:bjensen@fastmail.fm">mailto:bjensen@fastmail.fm</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 15, 2002 1:22 PM</FONT>
<BR><FONT SIZE=3D2>To: Smith, Wayne</FONT>
<BR><FONT SIZE=3D2>Cc: 'omniorb-list@omniorb-support.com'</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [omniORB] FW: Problem w/ Client/Server =
Communication Across</FONT>
<BR><FONT SIZE=3D2>LAN With Client /Server NameServices</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi Wayne,</FONT>
</P>

&nbsp; Yes, there is indeed a way to make omniNames =
have
 the same IOR on a particular host, at least =
for
 versions since 3.0.3. You need to start =
omniNames
 on the same port and interface, which it ought =
to
 do by itself, unless you are using dynamic =
IP's.
 If you must use dynamic IP's, you could tell
 omniORB to use hostnames instead, but then =
you
 need static hostnames instead of IP's....
 &nbsp; The entries, you are refering to, in the =
config
 file are used to configure the =
initial_references,
 and omniNames does not use them for anything.

<P><FONT SIZE=3D2>Yours sincerely,</FONT>
</P>

<P><FONT SIZE=3D2>Bjorn</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2753C.2EABE520--