pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aleksey Demakov <avd@gcom.ru>
To: pgsql-interfaces@postgresql.org
To: orbit-list@cuc.edu
Subject: Re: [INTERFACES] ORB API
Date: 17 Nov 1998 12:04:56 +0600
Message-ID: <87iugelura.fsf@avd.garsib.ru> (raw)
References: <000601be1175$f0ed9360$8a14f7d0@taral.dobiecenter.com>


Sorry, I don't know whether I'm right crossposting this to two
mailing lists. I hope that ORBit guys could comment better on this
post [this is discussion about choosing ORB for PostgreSQL].

Aleksey

"Taral" <taral@cyberjunkie.com> writes:

> > I believe that ORBit is the best candidate, though it's not yet
> > complete and its ability to interoperate with other implementations
> > is to be proven. But unlike others it doesn't require egcs or
> > OS thread support (omniORB). It is intended for real work, not
> > for education (mico). It is in active development wich we can
> > join to.
> 
> But does it fully support the basic CORBA 2.2 API *right now*? The point of
> using mico was that we can easily switch ORBs later on since the 2.2 API is
> so specific.
> 
> Example:
> 
> omniORB does not use the 2.2 perform_work()/run() functions, but instead has
> an extension to the impl_is_ready() function. Although their implementation
> is valid under 2.0, it is *not* valid under 2.2.
> 
> Taral
> 
> 
> 
> 

-- 
Aleksey Demakov
avd@gcom.ru



view thread (11+ messages)

Message-ID: <87iugelura.fsf@avd.garsib.ru>
Permalink:  ../87iugelura.fsf@avd.garsib.ru/
Also on:    postgresql.org/message-id/87iugelura.fsf@avd.garsib.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: avd@gcom.ru, orbit-list@cuc.edu
  Subject: Re: [INTERFACES] ORB API
  In-Reply-To: <87iugelura.fsf@avd.garsib.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox