[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Secure Sockets (was: Embedding foreign parts)
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-07-07 14:44:43
[Download RAW message or body]

On Wed, 7 Jul 1999, Leon Widdershoven wrote:

> 
> 
> On Wed, 7 Jul 1999, Simon Hausmann wrote:
> 
> > On Tue, 6 Jul 1999, Kurt Granroth wrote:
> > 
> > > Simon Hausmann wrote:
> > > > On Tue, 6 Jul 1999, Jo Dillon wrote:
> > > > >   Seems reasonable. Do the Gnome people have any ideas about this?
> > > > 
> > > > They implemented cookie-stuff into Orbit. This requires everyone to use
> > > > Orbit for CORBA based services in GNOME
> > > > 
> > > > => You can't use any other ORB than Orbit if you want to connect to a
> > > > GNOME CORBA server
> > > > :-(
> > > 
> > > By this statement, are we saying that you can use any ORB with KDE and
> > > we are not restricting everybody to MICO?  Why did I get the
> > > impression that we are a MICO-only shop?  Is this a wrong impression?
> > 
> > Yes, you can use every ORB to connect to a CORBA server in KDE. You just
> > need the IOR, but that's where kded is your friend (just grab the IOR from
> > the root-window and use the initialreferences interface) .
> 
> Hmmm. Am I right when I say that you need the MICO library to
> compile kded, but that after kded is compiled and running it
> can connect also to non-mico ORBs?

KDE requires MICO to compile, but you can use every ORB to connect to a
MICO based CORBA server.

> Or is also the CORBA API generic so you would not even need
> mico to compile kded but just any CORBA 2 compliant library?

No, KDE depends on MICO for compilation.

Ciao,
 Simon

[prev in list] [next in list] [prev in thread] [next in thread]