FW: [HACKERS] Re: CORBA Interface

From: Dan Gowin <DGowin(at)avantec(dot)net>
To: pgsql-hackers(at)hub(dot)org
Subject: FW: [HACKERS] Re: CORBA Interface
Date: 1998-11-12 15:57:15
Message-ID: 43A3A1806104D211988500A0C9B576EE5C4BC1@avantec_exc.avantec.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

-----Original Message-----
From: Dan Gowin
Sent: Thursday, November 12, 1998 10:46 AM
To: 'Cary B. O'Brien'
Subject: RE: [HACKERS] Re: CORBA Interface

All,
I agree with below. The ORB should be a seperate
daemon from the backend. Not only will the stability
of the backend be affected if the ORB is placed in the
backend, but performance will also suffer. The ORB should
be developed as a seperate daemon which -could- be placed
on a seperate server to increase performance. Also remember,
however the ORB is designed, it will consume alot of CPU
and memory resources within the server.

D.

-----Original Message-----
From: Cary B. O'Brien [mailto:cobrien(at)access(dot)digex(dot)net]
Sent: Thursday, November 12, 1998 10:00 AM
To: pgsql-hackers(at)hub(dot)org
Subject: [HACKERS] Re: CORBA Interface

1) A corba interface sounds interesting. I wish I had time
to investigate corba further.

2) Applixware proports to be able to access corba objects. I guess
this means it can import/export corba IDLs, and talk over IIOP?
I haven't tried it out.

3) I'm not sure that the interface needs to be part of the backend.
Most of the structure information can be obtained from the pg_
tables. Having a separate process would be safer for the overall
stability of the backend. Am I missing something?

In any case, it seems very worth investigating.

-- cary

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-11-12 16:30:00 Re: FW: [HACKERS] Re: CORBA Interface
Previous Message Thomas G. Lockhart 1998-11-12 15:17:24 Re: [HACKERS] A problem with the constraint system.