[Biocorba-l] Re: cvs.bioperl.org running ensembl perl corba

[Dickson, Mike]

See below:

> -----Original Message-----
> From: Brad Chapman [mailto:chapmanb@arches.uga.edu]
> Sent: Monday, April 16, 2001 9:14 PM
> To: biocorba-l@biocorba.org
> Cc: Chris Mungall
> Subject: Re: [Biocorba-l] Re: cvs.bioperl.org running ensembl 
> perl corba
> 
> 
> Hi Jason;
> Thanks for moving this to biocorba-l!
> 
> > Some other issues we are having - versions of ORBit > 0.5.3 
> (Brad - remind
> > us?)  are not playing nicely with CORBA::ORBit perl module.  
> 
> Okay, I think I got this all figured out last night. The 
> problem isn't 
> with CORBA::ORBit, the problem is with interoperability with other
> ORBs. ORBit versions >= 0.5.3 don't produce IIOP messages by
> default. The ORBit FAQ:
> 
> http://orbit-resource.sourceforge.net/faq.html
> 
> indicates that this is due to security concerns. So by default ORBit
> will only produce messages that ORBit can read. The flag 
> ORBIIOPIPv4=1 
> allows ORBit to produce valid IIOP that other ORBs can
> read. Putting this into /etc/orbitrc clears everything up and there
> are not interoperability concerns. ORBIIOPIPv4 specifies IIOP version
> 1.0, which is the standard, and ORBIIOPIPv6 specifies IIOP version
> 1.1, which I'm not positive is widely supported. So at least for me,
> sticking the v4 flag in there seems to clear up all concerns, 
> so ORBit 
> 0.5.7 works okay. Whew, so anyways, that's what I know.

Current orb iiop protocols are up to v1.2.  Everybody has to support v1.0 at
a minumum.  Later protocols add features (I believe 1.1 adds the ability to
share sockets and use an open socket bidirectionally amongst other things).
Most all Orbs I know of do 1.1 at least.  You should be fine using 1.0 at
least/until you see scalability problems with open connections.  I'd guess
that the MT behaviour is a bigger performance bottleneck issue than the
protocol version at this point.

Mike