Re: [HACKERS] CORBA interface in backend?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Michael Robinson <robinson(at)public(dot)bta(dot)net(dot)cn>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] CORBA interface in backend?
Date: 1998-11-11 05:54:12
Message-ID: Pine.BSF.4.05.9811110153490.337-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 11 Nov 1998, Michael Robinson wrote:

> I've been banging and banging my head against the specific problem of how
> to tightly couple the object-relational part of postgres with the object-
> list processing part of Python. In the midst of this head-banging, I thought
> of this possible general solution:
>
> Put an ORB in the backend.
>
> Not only would this, in theory, give fairly reasonable performance for
> persistent object store applications in Python, it would open up PostgreSQL
> for interoperability with any CORBA-interfaced application. Now that
> PostgreSQL has something of a stored procedural language, that makes it
> even more attractive.
>
> What I envision is a "dumpIDL" command that, for certain input parameters
> (table/class) would dump the appropriate IDL definition for instances(rows)
> of that class and related methods(functions). And then hack an existing
> ORB onto the backend to do all the translation, communications and
> bookkeeping.
>
> So, I'm soliciting opinions: is this brain fart worth pursuing, or should
> I just forget it ever happened?

How would this tie into the existing system? Does this become an
extension of it, or replace parts of it?

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Taral 1998-11-11 06:52:28 RE: [HACKERS] CORBA interface in backend?
Previous Message Michael Robinson 1998-11-11 05:33:52 CORBA interface in backend?