From mail-list@molnir.com Tue Nov  9 01:35:53 1999
Received: from mail.fasthosts.co.uk ([195.188.129.9])
	by hub.org (8.9.3/8.9.3) with ESMTP id UAA22666;
	Mon, 8 Nov 1999 20:35:53 -0500 (EST)
	(envelope-from mail-list@molnir.com)
Received: from tosh3 [195.147.169.222] by mail.fasthosts.co.uk
	(SMTPD32-5.05 EVAL) id ABB720C0150; Tue, 09 Nov 1999 01:41:11 +0000
Reply-To: <mail-list@molnir.com>
From: "Mark Proctor" <mail-list@molnir.com>
To: <pgsql-interfaces@postgresql.org>, <pgsql-hackers@postgresql.org>
Subject: CORBA STATUS
Date: Tue, 9 Nov 1999 01:38:35 -0000
Message-ID: <001401bf2a53$23d22510$dea993c3@tosh3>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0015_01BF2A53.23D22510"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01BF2A53.23D22510
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I'm currently studying for a Masters at Brunel University, London. I was
looking for a thesis and since I had an interest in Opensource development
and databases I thought that I would like to work on PGsql.  As I also had
an interest in trying to understand CORBA and other related technologies it
made sense that I try and work on a project that ties PGsql and CORBA
together in some way.

Marc G. Fournier and Bruce Momjian were contacted with regards to this and
they seemed to think that there was room for me to work on this, although at
this stage I hadn't gone through the mailing list.

since then I've finally got PGsql up and working and I'm now embarking on
understand how to system actual works. I thought a good place to start with
my research would be to go through the mailing lists to try and see the
current status for development in this area. I did this for several hours
trying to get the current take on CORBA with regards to PGsql. It seems
there was a lot of initial talk back in Nov 1998 on the hackers list with
the first thoughts of some sort of CORBA implementation. The conversation
orientated over 2 main areas; which ORB and implementation methods, with
some peoples offering to work on this. It was then suggested that the
converstaion take place in the interfaces mailing list. I've since been over
some of this but find it very difficult to understand the current status
with regards to PGsql and CORBA. I've seen many references to people who
have developed
a project that allows them to work with PGsql via CORBA, but non of this
seems to be part of the main project or system. There is some reference to
Micheal Robinson working on an implementation but again I'm not sure how
this fits
in-http://www.postgresql.org/mhonarc/pgsql-interfaces/1998-11/msg00090.html

Is there room for me to work on this project in such a way that it is
adequate for my masters. If anyone is working on this, or has a good
knowledge of the current status of the CORBA implementation for PGsql can
you please let me know, so I can know whether to get started on this or not.
The reference thread for my initial point of contact with Marc G. Fournier
and Bruce Momjian and how they think I should attack the project is -
http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.html

Regards

Mark Proctor
email : m.proctor@bigfoot.com


------=_NextPart_000_0015_01BF2A53.23D22510
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2><FONT face=3DArial>I'm currently studying for a =
Masters at=20
Brunel<SPAN class=3D893383001-09111999> </SPAN>University, London. I was =
looking=20
for a thesis and<SPAN class=3D893383001-09111999> </SPAN>since I had an =
interest=20
in<SPAN class=3D893383001-09111999> </SPAN>Opensource development =
and<SPAN=20
class=3D893383001-09111999> </SPAN>databases I thought that I would like =
to work=20
on<SPAN class=3D893383001-09111999> </SPAN>PGsql.&nbsp; As I also had an =
interest=20
in trying to<SPAN class=3D893383001-09111999> </SPAN>understand CORBA =
and other=20
related technologies it<SPAN class=3D893383001-09111999> </SPAN>made =
sense that I=20
try and work on a project that ties<SPAN class=3D893383001-09111999> =
</SPAN>PGsql=20
and CORBA together in some way.<BR><BR>Marc G. Fournier and Bruce =
Momjian were=20
contacted with<SPAN class=3D893383001-09111999> </SPAN>regards to this =
and they=20
seemed to think that there<SPAN class=3D893383001-09111999> </SPAN>was =
room for me=20
to work on this, although at this<SPAN class=3D893383001-09111999> =
</SPAN>stage I=20
hadn't gone through the mailing list.<BR><BR>since then I've finally got =
PGsql=20
up and working and<SPAN class=3D893383001-09111999> </SPAN>I'm now =
embarking on=20
understand how to system actual<SPAN class=3D893383001-09111999> =
</SPAN>works. I=20
thought a good place to start with my<SPAN class=3D893383001-09111999>=20
</SPAN>research would be to go through the mailing lists to<SPAN=20
class=3D893383001-09111999> </SPAN>try and see the current status for =
development=20
in this<SPAN class=3D893383001-09111999> </SPAN>area. I did this for =
several hours=20
trying to get the<SPAN class=3D893383001-09111999> </SPAN>current take =
on CORBA=20
with regards to PGsql. It seems<SPAN class=3D893383001-09111999> =
</SPAN>there was=20
a lot of initial talk back in Nov 1998 on<SPAN =
class=3D893383001-09111999>=20
</SPAN>the hackers list with the first thoughts of some sort<SPAN=20
class=3D893383001-09111999> </SPAN>of CORBA implementation. The =
conversation=20
orientated<SPAN class=3D893383001-09111999> </SPAN>over 2 main areas; =
which ORB=20
and implementation<SPAN class=3D893383001-09111999> </SPAN>methods, with =
some=20
peoples offering to work on this.<SPAN class=3D893383001-09111999> =
</SPAN>It was=20
then suggested that the converstaion take place<SPAN =
class=3D893383001-09111999>=20
</SPAN>in the interfaces mailing list. I've since been over<SPAN=20
class=3D893383001-09111999> </SPAN>some of this but find it very =
difficult to=20
understand<SPAN class=3D893383001-09111999> </SPAN>the current status =
with regards=20
to PGsql and CORBA.<SPAN class=3D893383001-09111999> </SPAN>I've seen =
many=20
references to people who have developed<BR>a project that allows them to =
work=20
with PGsql via<SPAN class=3D893383001-09111999> </SPAN>CORBA, but non of =
this=20
seems to be part of the main<SPAN class=3D893383001-09111999> =
</SPAN>project<SPAN=20
class=3D893383001-09111999> or system</SPAN>. There is some reference to =
Micheal=20
Robinson<SPAN class=3D893383001-09111999> </SPAN>working on an =
implementation but=20
again I'm not sure<SPAN class=3D893383001-09111999> </SPAN>how this fits =
in<SPAN=20
class=3D893383001-09111999>-http://www.postgresql.org/mhonarc/pgsql-inter=
faces/1998-11/msg00090.html</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D893383001-09111999></SPAN><BR>Is there=20
room for me to work on this project in such a<SPAN =
class=3D893383001-09111999>=20
</SPAN>way that it is adequate for my masters. If anyone is<SPAN=20
class=3D893383001-09111999> </SPAN>working on this, or has a good =
knowledge of=20
the<SPAN class=3D893383001-09111999> </SPAN>current status of the CORBA=20
implementation for PGsql<SPAN class=3D893383001-09111999> </SPAN>can you =
please=20
let me know, so I can know whether to<SPAN class=3D893383001-09111999> =
</SPAN>get=20
started on this or not. The reference thread for<SPAN =
class=3D893383001-09111999>=20
</SPAN>my initial point of contact with Marc G. Fournier and<SPAN=20
class=3D893383001-09111999> </SPAN>Bruce Momjian and how they think I =
should=20
attack the<SPAN class=3D893383001-09111999> </SPAN>project is -<SPAN=20
class=3D893383001-09111999> </SPAN><A=20
href=3D"http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.=
html"=20
target=3D_blank>http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/m=
sg00076.html</A><BR><BR>Regards<BR><BR>Mark=20
Proctor<BR>email : <A=20
href=3D"http://f1.mail.yahoo.com/ym/Compose?To=3Dm.proctor@bigfoot.com&am=
p;YY=3D6568&amp;order=3Ddown&amp;sort=3Ddate&amp;pos=3D0">m.proctor@bigfo=
ot.com</A><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_0015_01BF2A53.23D22510--




From maillist@candle.pha.pa.us Tue Nov  9 02:31:27 1999
Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67])
	by hub.org (8.9.3/8.9.3) with ESMTP id VAA30144;
	Mon, 8 Nov 1999 21:31:27 -0500 (EST)
	(envelope-from maillist@candle.pha.pa.us)
Received: (from maillist@localhost)
	by candle.pha.pa.us (8.9.0/8.9.0) id VAA01965;
	Mon, 8 Nov 1999 21:09:51 -0500 (EST)
From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199911090209.VAA01965@candle.pha.pa.us>
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <001401bf2a53$23d22510$dea993c3@tosh3> from Mark Proctor at "Nov
	9, 1999 01:38:35 am"
To: mail-list@molnir.com
Date: Mon, 8 Nov 1999 21:09:51 -0500 (EST)
CC: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> Is there room for me to work on this project in such a way that it is
> adequate for my masters. If anyone is working on this, or has a good
> knowledge of the current status of the CORBA implementation for PGsql can
> you please let me know, so I can know whether to get started on this or not.
> The reference thread for my initial point of contact with Marc G. Fournier
> and Bruce Momjian and how they think I should attack the project is -
> http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.html

I know of no one working on it.  There were two ideas as I remember. 
One was to replace our existing client/server communication with corba,
and the second was to have a corba server that accepted corba requests
and sent them to a PostgreSQL server.  I prefer this second approach as
I think CORBA may be too much overhead for people who don't need it. 
Our current client/server communication is quite efficient.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



From lockhart@alumni.caltech.edu Tue Nov  9 07:48:29 1999
Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203])
	by hub.org (8.9.3/8.9.3) with ESMTP id CAA70829;
	Tue, 9 Nov 1999 02:48:29 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id HAA04336;
	Tue, 9 Nov 1999 07:55:37 GMT
Sender: lockhart@hub.org
Message-ID: <3827D379.F9FCC38D@alumni.caltech.edu>
Date: Tue, 09 Nov 1999 07:55:37 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mail-list@molnir.com
CC: Bruce Momjian <maillist@candle.pha.pa.us>,
 pgsql-interfaces@postgreSQL.org,
	pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <199911090209.VAA01965@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> > Is there room for me to work on this project in such a way that it is
> > adequate for my masters. If anyone is working on this, or has a good
> > knowledge of the current status of the CORBA implementation for PGsql can
> > you please let me know, so I can know whether to get started on this or not.
> > The reference thread for my initial point of contact with Marc G. Fournier
> > and Bruce Momjian and how they think I should attack the project is -
> > http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.html
> I know of no one working on it.

Right. No one is working on it, or if they are they haven't told
anyone. It's all yours ;)

> There were two ideas as I remember.
> One was to replace our existing client/server communication with corba,
> and the second was to have a corba server that accepted corba requests
> and sent them to a PostgreSQL server.  I prefer this second approach as
> I think CORBA may be too much overhead for people who don't need it.
> Our current client/server communication is quite efficient.

Actually, our current protocol is about the best you can do assuming
that you don't have something as powerful as Corba to do it right.

In the time since Corba was first brought up wrt Postgres, I have been
involved with extensive Corba development for a family of systems at
work. It is a tremendously powerful standard, though just
re-implementing the existing interfaces using Corba would probably
defeat the power and flexibility Corba can give you.

Postgres currently avoids endian and other data representation issues
between client and server by converting all data to strings. Corba can
efficiently pass binary info back and forth, automatically handling
endian issues *if necessary*. This alone should make a Corba-based
interface using native internal representations of data types more
efficient both in speed and size than our current scheme.

Using Corba's DII, we might even cope with Postgres' type
extensibility features in a transparent manner.

One trick will be to choose a Corba ORB to use on the server side. It
should probably be a C implementation, though Corba more naturally
maps to an OO language such as C++. It will be a trick to find an ORB
which is supported on as many platforms as Postgres is. One of the
most portable ORBs is TAO, which we are using at work, but that is C++
and involves 1.3GB of disk space to fully build!! But the runtime
sizes are pretty reasonable, adding just a few megabytes of shared
libraries to a plain-vanilla client/server application.

imho it will be extremely difficult to find an ORB which could be
injected directly into the Postgres server. It would likely reduce the
number of platforms Postgres runs on, and would not be considered
acceptable.

For a first cut, you might consider Bruce's "plan B", which involves
writing a new client to the Postgres backend, which would be a Corba
server to other clients. That would allow you to start working with
Corba without hacking up the backend early on.

At the extreme end, fully Corba-ized Postgres server is an intriguing
thought, allowing backend to be broken up into distributable modules.

Have fun thinking about the possibilities...

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From petermount@it.maidstone.gov.uk Tue Nov  9 08:42:42 1999
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net
	[194.217.242.20]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA80988;
	Tue, 9 Nov 1999 03:42:42 -0500 (EST)
	(envelope-from petermount@it.maidstone.gov.uk)
Received: from mailgate.maidstone.gov.uk ([194.159.6.98]
	helo=gatekeeper.maidstone.gov.uk)
	by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2)
	id 11l6rN-000FJn-0K; Tue, 9 Nov 1999 08:42:37 +0000
Received: from exchange1.nt.maidstone.gov.uk (exchange1.nt.maidstone.gov.uk
	[172.16.0.150])
	by gatekeeper.maidstone.gov.uk (8.9.3/8.9.3) with ESMTP id JAA03726;
	Tue, 9 Nov 1999 09:59:39 GMT
Received: by exchange1.nt.maidstone.gov.uk with Internet Mail Service
	(5.5.1960.3) id <T6GA5P0P>; Tue, 9 Nov 1999 08:40:05 -0000
Message-ID: 
 <1B3D5E532D18D311861A00600865478C25E81E@exchange1.nt.maidstone.gov.uk>
From: Peter Mount <petermount@it.maidstone.gov.uk>
To: "'Bruce Momjian'" <maillist@candle.pha.pa.us>, mail-list@molnir.com
Cc: pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org
Subject: RE: [HACKERS] CORBA STATUS
Date: Tue, 9 Nov 1999 08:40:04 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

I agree with you Bruce, as replacing the current protocol with IIOP
would IMHO be a bad idea, and possibly not be implementable on some
platforms.

PS: Theres a Corba/Java example in the source. Works only for Java2 (as
it has a limited orb).

Peter

> -----Original Message-----
> From:	Bruce Momjian [SMTP:maillist@candle.pha.pa.us]
> Sent:	09 November 1999 02:10
> To:	mail-list@molnir.com
> Cc:	pgsql-interfaces@postgreSQL.org; pgsql-hackers@postgreSQL.org
> Subject:	Re: [HACKERS] CORBA STATUS
> 
> > Is there room for me to work on this project in such a way that it
> is
> > adequate for my masters. If anyone is working on this, or has a good
> > knowledge of the current status of the CORBA implementation for
> PGsql can
> > you please let me know, so I can know whether to get started on this
> or not.
> > The reference thread for my initial point of contact with Marc G.
> Fournier
> > and Bruce Momjian and how they think I should attack the project is
> -
> >
> http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.html
> 
> I know of no one working on it.  There were two ideas as I remember. 
> One was to replace our existing client/server communication with
> corba,
> and the second was to have a corba server that accepted corba requests
> and sent them to a PostgreSQL server.  I prefer this second approach
> as
> I think CORBA may be too much overhead for people who don't need it. 
> Our current client/server communication is quite efficient.
> 
> -- 
>   Bruce Momjian                        |  http://www.op.net/~candle
>   maillist@candle.pha.pa.us            |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania
> 19026
> 
> ************



From geek+@cmu.edu Tue Nov  9 13:15:31 1999
Received: from smtp3.andrew.cmu.edu (SMTP3.ANDREW.CMU.EDU [128.2.10.83])
	by hub.org (8.9.3/8.9.3) with ESMTP id IAA13915;
	Tue, 9 Nov 1999 08:15:31 -0500 (EST) (envelope-from geek+@cmu.edu)
Received: from export.andrew.cmu.edu (EXPORT.ANDREW.CMU.EDU [128.2.23.2])
	by smtp3.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id IAA02767;
	Tue, 9 Nov 1999 08:15:30 -0500 (EST)
Date: 9 Nov 1999 08:15:30 -0500
Message-ID: <emacs-smtp-589-14376-7794-234999@export.andrew.cmu.edu>
From: Brian E Gallew <geek+@cmu.edu>
X-Mailer: BatIMail version 3.2
To: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
In-reply-to: <3827D379.F9FCC38D@alumni.caltech.edu>
Subject: Re: [HACKERS] CORBA STATUS
References: <199911090209.VAA01965@candle.pha.pa.us>
	<3827D379.F9FCC38D@alumni.caltech.edu>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/signed; protocol="application/pgp-signature";
	boundary="pgp-sign-Multipart_Tue_Nov__9_08:15:29_1999-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit

--pgp-sign-Multipart_Tue_Nov__9_08:15:29_1999-1
Content-Type: text/plain; charset=US-ASCII

Then <lockhart@alumni.caltech.edu> spoke up and said:
> imho it will be extremely difficult to find an ORB which could be
> injected directly into the Postgres server. It would likely reduce the
> number of platforms Postgres runs on, and would not be considered
> acceptable.

On the other hand, this is where the power of configure comes into
play.  Assuming we have servers for multiple ORBs, configure can look
to see what's installed (TAO, Orbit, whatever) and then build only
that server.

-- 
=====================================================================
| JAVA must have been developed in the wilds of West Virginia.      |
| After all, why else would it support only single inheritance??    |
=====================================================================
| Finger geek@cmu.edu for my public key.                            |
=====================================================================

--pgp-sign-Multipart_Tue_Nov__9_08:15:29_1999-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface

iQBVAwUBOCgecYdzVnzma+gdAQELYwIAsYYJi3E7ovCRXtYQjuGx48xdd/+d8QI8
BjxG2YvbrxFZTEqT2YG8f53uN4FCIvW1hz7AXT5567iNTv0fhSvEOQ==
=LKwr
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Tue_Nov__9_08:15:29_1999-1--




From scrappy@hub.org Tue Nov  9 14:12:39 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA21964;
	Tue, 9 Nov 1999 09:12:39 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA40956;
	Tue, 9 Nov 1999 10:12:56 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 9 Nov 1999 10:12:56 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Brian E Gallew <geek+@cmu.edu>
cc: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <emacs-smtp-589-14376-7794-234999@export.andrew.cmu.edu>
Message-ID: <Pine.BSF.4.10.9911091011530.2296-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On 9 Nov 1999, Brian E Gallew wrote:

> Then <lockhart@alumni.caltech.edu> spoke up and said:
> > imho it will be extremely difficult to find an ORB which could be
> > injected directly into the Postgres server. It would likely reduce the
> > number of platforms Postgres runs on, and would not be considered
> > acceptable.
> 
> On the other hand, this is where the power of configure comes into
> play.  Assuming we have servers for multiple ORBs, configure can look
> to see what's installed (TAO, Orbit, whatever) and then build only
> that server.

ACtually, I believe Thomas was referring to those platforms that we
currently support that have no ORBs available to them...being a "purely C"
server so far, how many of our currently supported platforms are we going
to cut off with this? 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




From geek+@cmu.edu Tue Nov  9 14:44:29 1999
Received: from smtp2.andrew.cmu.edu (SMTP2.ANDREW.CMU.EDU [128.2.10.82])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA26872;
	Tue, 9 Nov 1999 09:44:29 -0500 (EST) (envelope-from geek+@cmu.edu)
Received: from export.andrew.cmu.edu (EXPORT.ANDREW.CMU.EDU [128.2.23.2])
	by smtp2.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id JAA09368;
	Tue, 9 Nov 1999 09:44:28 -0500 (EST)
Date: 9 Nov 1999 09:44:27 -0500
Message-ID: <emacs-smtp-589-14376-13131-719199@export.andrew.cmu.edu>
From: Brian E Gallew <geek+@cmu.edu>
X-Mailer: BatIMail version 3.2
To: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org
In-reply-to: <Pine.BSF.4.10.9911091011530.2296-100000@thelab.hub.org>
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911091011530.2296-100000@thelab.hub.org>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/signed; protocol="application/pgp-signature";
	boundary="pgp-sign-Multipart_Tue_Nov__9_09:44:26_1999-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit

--pgp-sign-Multipart_Tue_Nov__9_09:44:26_1999-1
Content-Type: text/plain; charset=US-ASCII

Then <scrappy@hub.org> spoke up and said:
> ACtually, I believe Thomas was referring to those platforms that we
> currently support that have no ORBs available to them...being a "purely C"
> server so far, how many of our currently supported platforms are we going
> to cut off with this? 

But that's just it: we're not cutting anybody off.  We may not have a
CORBA server available for that platform, but the standard server will
continue to work quite nicely.  I guess that I'm looking at this more
as contrib code than as mainstream, required functionality.  Besides,
once the CORBA server is built on a platform that can support it,
clients can run from (basically) anywhere.

-- 
=====================================================================
| JAVA must have been developed in the wilds of West Virginia.      |
| After all, why else would it support only single inheritance??    |
=====================================================================
| Finger geek@cmu.edu for my public key.                            |
=====================================================================

--pgp-sign-Multipart_Tue_Nov__9_09:44:26_1999-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.3, an Emacs/PGP interface

iQBVAwUBOCgzS4dzVnzma+gdAQFBlAIAnBidfugkYxLPCdv/BgNDkZggbJGhNZxL
SOTUTMStTRlDjwmBu2SaQqd5xdMNH/RiaqyAT4sqR/p03fRYW879GQ==
=c6ru
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Tue_Nov__9_09:44:26_1999-1--




From lockhart@alumni.caltech.edu Tue Nov  9 14:59:47 1999
Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA30329;
	Tue, 9 Nov 1999 09:59:47 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id PAA04868;
	Tue, 9 Nov 1999 15:06:54 GMT
Sender: lockhart@hub.org
Message-ID: <3828388D.3EC63B4B@alumni.caltech.edu>
Date: Tue, 09 Nov 1999 15:06:53 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: Brian E Gallew <geek+@cmu.edu>, pgsql-hackers@postgreSQL.org,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911091011530.2296-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> > > imho it will be extremely difficult to find an ORB which could be
> > > injected directly into the Postgres server. It would likely reduce the
> > > number of platforms Postgres runs on, and would not be considered
> > > acceptable.
> > On the other hand, this is where the power of configure comes into
> > play.  Assuming we have servers for multiple ORBs, configure can look
> > to see what's installed (TAO, Orbit, whatever) and then build only
> > that server.

In the long run, that would be neat. In the short run, the details of
each ORB vary considerably wrt, for example, the names and numbers of
#include files. So it would complicate the code to try bringing along
two ORBs at the beginning. We might expect the ORBs to converge a bit
over time, so this will be easier later.

> ACtually, I believe Thomas was referring to those platforms that we
> currently support that have no ORBs available to them...being a "purely C"
> server so far, how many of our currently supported platforms are we going
> to cut off with this?

Don't know, and it doesn't matter (yet). We shouldn't avoid the issue
without someone looking at it further just because we *might* lose
some platforms; better to push it farther as a demonstration at least
before deciding that it isn't a possibility.

Anyway, I know that at least one ORB, TAO, runs on many more types of
platforms than Postgres does (e.g. VxWorks, Lynx, Solaris, NT, ...),
though Postgres runs on more Unix-style platforms. But that particular
ORB is not a good candidate for us, for reasons I already mentioned
(C++, large build size, poor configure support).

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From horak@mmp.plzen-city.cz Tue Nov  9 15:21:57 1999
Received: from gate.plzen-city.cz (gate.plzen-city.cz [194.212.191.10])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA34963;
	Tue, 9 Nov 1999 10:21:57 -0500 (EST)
	(envelope-from horak@mmp.plzen-city.cz)
Received: (from mail@localhost)
	by gate.plzen-city.cz (8.9.3/8.9.1) id QAA18268;
	Tue, 9 Nov 1999 16:21:51 +0100
Received: from EXCHANGE.mmp.plzen-city.cz(s5srvr1.mmp.plzen-city.cz
	192.168.51.21) by gate.plzen-city.cz via smap (v1.3-ps12tp)
	id sma018251; Tue Nov  9 16:19:02 1999
Received: by exchange.mmp.plzen-city.cz with Internet Mail Service
	(5.5.2650.21) id <WQVHDXFJ>; Tue, 9 Nov 1999 16:19:01 +0100
Message-ID: 
 <2E7F82FAC1FCD2118E1500A024B3BF907DEDF0@exchange.mmp.plzen-city.cz>
From: Horak Daniel <horak@mmp.plzen-city.cz>
To: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org
Subject: RE: [HACKERS] CORBA STATUS
Date: Tue, 9 Nov 1999 16:19:01 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

> Anyway, I know that at least one ORB, TAO, runs on many more types of
> platforms than Postgres does (e.g. VxWorks, Lynx, Solaris, NT, ...),
> though Postgres runs on more Unix-style platforms. But that particular
> ORB is not a good candidate for us, for reasons I already mentioned
> (C++, large build size, poor configure support).

Only a small note (I don't know details): there is an implementation of
CORBA for the Gnome desktop called ORBit (small, in C, fast), please see
http://www.labs.redhat.com/orbit/

			Dan



From dms@wplus.net Tue Nov  9 17:57:03 1999
Received: from ritchie.wplus.net (relay.wplus.net [195.131.52.179])
	by hub.org (8.9.3/8.9.3) with ESMTP id MAA64006;
	Tue, 9 Nov 1999 12:57:03 -0500 (EST)
	(envelope-from dms@woland.wplus.net)
Received: from woland.wplus.net (woland.wplus.net [195.131.0.39])
	by ritchie.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id UAA00699;
	Tue, 9 Nov 1999 20:56:19 +0300 (MSK/MSD)
X-Real-To: scrappy@hub.org
Received: (from dms@localhost)
	by woland.wplus.net (8.9.3/8.9.1/wplus.2) id UAA51679;
	Tue, 9 Nov 1999 20:56:19 +0300 (MSK)
Message-ID: <XFMail.991109205619.dms@wplus.net>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <3828388D.3EC63B4B@alumni.caltech.edu>
Date: Tue, 09 Nov 1999 20:56:19 +0400 (MSK)
Sender: dms@woland.wplus.net
From: Dmitry Samersoff <dms@wplus.net>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Subject: Re: [HACKERS] CORBA STATUS
Cc: pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org,
	Brian E Gallew <geek+@cmu.edu>, The Hermit Hacker <scrappy@hub.org>


On 09-Nov-99 Thomas Lockhart wrote:
>> > > imho it will be extremely difficult to find an ORB which could be
>> > > injected directly into the Postgres server. It would likely reduce the
>> > > number of platforms Postgres runs on, and would not be considered
>> > > acceptable.
>> > On the other hand, this is where the power of configure comes into
>> > play.  Assuming we have servers for multiple ORBs, configure can look
>> > to see what's installed (TAO, Orbit, whatever) and then build only
>> > that server.
> 
> In the long run, that would be neat. In the short run, the details of
> each ORB vary considerably wrt, for example, the names and numbers of
>#include files. So it would complicate the code to try bringing along
> two ORBs at the beginning. We might expect the ORBs to converge a bit
> over time, so this will be easier later.
> 
>> ACtually, I believe Thomas was referring to those platforms that we
>> currently support that have no ORBs available to them...being a "purely C"
>> server so far, how many of our currently supported platforms are we going
>> to cut off with this?
> 
> Don't know, and it doesn't matter (yet). We shouldn't avoid the issue
> without someone looking at it further just because we *might* lose
> some platforms; better to push it farther as a demonstration at least
> before deciding that it isn't a possibility.
> 
> Anyway, I know that at least one ORB, TAO, runs on many more types of
> platforms than Postgres does (e.g. VxWorks, Lynx, Solaris, NT, ...),
> though Postgres runs on more Unix-style platforms. But that particular
> ORB is not a good candidate for us, for reasons I already mentioned
> (C++, large build size, poor configure support).

IMHO, There has no ideal ORB for all platforms.
we use ORBacus (http://www.ooc.com), 
because it's the only known for me ORB, working without threads 
so its really faster and more stable than another ones under FreeBSD,
but it's not free.

May be it is better make directory CORBA under interfaces subtree
and time-to-time put objects for differend ORB's inside, 
into separate directory.

Probably, It's better to make separate configure for 
some parts of postgres distributions to allow users to build/upgrade
parts of postgres i.e psql or perl interface 




---
Dmitry Samersoff, dms@wplus.net, ICQ:3161705
http://devnull.wplus.net
* There will come soft rains ...



From goran@kirra.net Tue Nov  9 17:16:07 1999
Received: from villa.bildbasen.se (villa.bildbasen.kiruna.se [193.45.225.97])
	by hub.org (8.9.3/8.9.3) with SMTP id MAA57983
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 9 Nov 1999 12:16:07 -0500 (EST) (envelope-from goran@kirra.net)
Received: (qmail 11942 invoked from network); 9 Nov 1999 17:15:10 -0000
Received: from a212.dial.kiruna.se (HELO kirra.net) (193.45.238.28)
	by villa.bildbasen.kiruna.se with SMTP; 9 Nov 1999 17:15:10 -0000
Sender: goran
Message-ID: <3828569A.3BE41F94@kirra.net>
Date: Tue, 09 Nov 1999 18:15:06 +0100
From: Goran Thyni <goran@kirra.net>
Organization: kirra.net
X-Mailer: Mozilla 4.6 [en] (X11; U; Linux 2.2.13 i586)
X-Accept-Language: sv, en
MIME-Version: 1.0
To: mail-list@molnir.com
CC: pgsql-interfaces@postgreSQL.org, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <001401bf2a53$23d22510$dea993c3@tosh3>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


I have done some research into slapping
a CORBA interface onto the PgSQL server.
I have looked at ORBit but my findings 
seems to apply to most CORBA implementations.

I found that there is a fundamental problem
concerning the difference in process models
in pgsql and the POA (Portable Object Adaptor)
in CORBA implementations.

AFAICS, POA assumes a threaded server while
PgSQL uses a traditional forking model.

I see 3 ways to resolve this:

1. Adapt the PgSQL server to use threads instead of forking.
   I am not sure we want to do this since it is a major
   undertaking and will not help the rock solid stability
   we expect from a professional RDBMS.

2. Write a Forking Object Adaptor (FOA).
   Would be a big job but it would benefit other similar
   projects. A FOA would have to be rewritten for every
   ORB. If you want to do this I suggest starting with
   ORBit since it is all C and thereby easier to slap
   onto PgSQL.

3. Extend postmaster to proxy CORBA requests.
   Postmaster could fork of postgres processes
   on incoming connections. Postmaster will keep 
   listening and proxying request and responses 
   to/from the postgres process through some kind
   of IPC. This will make the postmaster multithreaded 
   and the postgres processes still singlethreaded.

It is doubtful if the gains:
- standard-based protocols
- less code to maintain (?)
justifies the amount of work required.

An easier way out is to, as suggested by others,
implement the CORBA-service outside the server
itself. It will in some cases give some latency
related performance degrading compared to a 
in-server implementation.

One effort to do something like that
(and more) is gnome-db. Check out
http://www.gnome.org/gnome-db/

regards,
-----------------
Göran Thyni
On quiet nights you can hear Windows NT reboot!



From a.joubert@albourne.com Tue Nov  9 17:15:24 1999
Received: from sapphire.albourne.com (root@sapphire.albourne.com
	[195.212.241.227]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA57923;
	Tue, 9 Nov 1999 12:15:24 -0500 (EST)
	(envelope-from a.joubert@albourne.com)
Received: from isadora.cy.albourne.com (akamas.albourne.com [195.212.241.254])
	by sapphire.albourne.com (8.9.3/8.9.3/Albourne/CYS/1.6X) with ESMTP
	id TAA11936; Tue, 9 Nov 1999 19:18:52 +0200 (EET)
Received: from albourne.com (localhost [127.0.0.1])
	by isadora.cy.albourne.com (8.9.3/8.9.3/Albourne/CYC/1.4) with ESMTP id
	TAA07738; Tue, 9 Nov 1999 19:15:17 +0200 (EET)
Sender: a.joubert@albourne.com
Message-ID: <382856A5.DBC80BE@albourne.com>
Date: Tue, 09 Nov 1999 19:15:17 +0200
From: Adriaan Joubert <a.joubert@albourne.com>
Organization: APL Financial Services (Overseas) Ltd
X-Mailer: Mozilla 4.61 [en] (X11; U; OSF1 V4.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: Brian E Gallew <geek+@cmu.edu>, pgsql-hackers@postgreSQL.org,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911091011530.2296-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> ACtually, I believe Thomas was referring to those platforms that we
> currently support that have no ORBs available to them...being a "purely C"
> server so far, how many of our currently supported platforms are we going
> to cut off with this?

OmniORB http://www.uk.research.att.com/omniORB/omniORBForm.html runs on
most
Unix-like platforms. It is free and it is pretty fast. I used it a about
18 months ago and it was already pretty good then.

Adriaan



From phd@phd.russ.ru Tue Nov  9 18:25:36 1999
Received: from fep132.fep.ru (mail@fep132.fep.ru [195.230.89.88])
	by hub.org (8.9.3/8.9.3) with ESMTP id NAA68138;
	Tue, 9 Nov 1999 13:25:36 -0500 (EST) (envelope-from phd@phd.russ.ru)
Received: from localhost [127.0.0.1] (phd)
	by fep132.fep.ru with esmtp (Exim 2.05 #1 (Debian))
	id 11lFxL-0008BU-00; Tue, 9 Nov 1999 21:25:23 +0300
Date: Tue, 9 Nov 1999 18:25:23 +0000 (GMT)
From: Oleg Broytmann <phd@phd.russ.ru>
X-Sender: phd@fep132.fep.ru
Reply-To: phd2@earthling.net
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
cc: pgsql-interfaces@postgresql.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <XFMail.991109205619.dms@wplus.net>
Message-ID: <Pine.LNX.4.20.9911091822550.31442-100000@fep132.fep.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 9 Nov 1999, Dmitry Samersoff wrote:
> > Anyway, I know that at least one ORB, TAO, runs on many more types of
> > platforms than Postgres does (e.g. VxWorks, Lynx, Solaris, NT, ...),
> > though Postgres runs on more Unix-style platforms. But that particular
> > ORB is not a good candidate for us, for reasons I already mentioned
> > (C++, large build size, poor configure support).
> 
> IMHO, There has no ideal ORB for all platforms.
> we use ORBacus (http://www.ooc.com), 
> because it's the only known for me ORB, working without threads 
> so its really faster and more stable than another ones under FreeBSD,
> but it's not free.

   FNORB - http://www.dstc.edu.au/Products/Fnorb/
   Fnorb is a CORBA 2.0 ORB written in Python. Free for non-commercial
use.

Oleg.
---- 
    Oleg Broytmann     http://members.xoom.com/phd2/     phd2@earthling.net
           Programmers don't die, they just GOSUB without RETURN.




From petermount@it.maidstone.gov.uk Tue Nov  9 21:33:06 1999
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net
	[194.217.242.20]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA98987;
	Tue, 9 Nov 1999 16:33:06 -0500 (EST)
	(envelope-from petermount@it.maidstone.gov.uk)
Received: from mailgate.maidstone.gov.uk ([194.159.6.98]
	helo=gatekeeper.maidstone.gov.uk)
	by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2)
	id 11lIsx-0005Vu-0K; Tue, 9 Nov 1999 21:33:03 +0000
Received: from exchange1.nt.maidstone.gov.uk (exchange1.nt.maidstone.gov.uk
	[172.16.0.150])
	by gatekeeper.maidstone.gov.uk (8.9.3/8.9.3) with ESMTP id WAA06313;
	Tue, 9 Nov 1999 22:50:20 GMT
Received: by exchange1.nt.maidstone.gov.uk with Internet Mail Service
	(5.5.1960.3) id <T6GA5QGD>; Tue, 9 Nov 1999 21:30:30 -0000
Message-ID: 
 <1B3D5E532D18D311861A00600865478C25E82C@exchange1.nt.maidstone.gov.uk>
From: Peter Mount <petermount@it.maidstone.gov.uk>
To: "'Dmitry Samersoff'" <dms@wplus.net>, Thomas Lockhart
	<lockhart@alumni.caltech.edu>
Cc: pgsql-interfaces@postgresql.org, pgsql-hackers@postgresql.org,
	Brian E Gallew <geek+@cmu.edu>, The Hermit Hacker <scrappy@hub.org>
Subject: RE: [HACKERS] CORBA STATUS
Date: Tue, 9 Nov 1999 21:30:26 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain

IMHO, I think this would be better for the short term.

Peter

> -----Original Message-----
> From:	Dmitry Samersoff [SMTP:dms@wplus.net]
> Sent:	09 November 1999 16:56
> To:	Thomas Lockhart
> Cc:	pgsql-interfaces@postgreSQL.org; pgsql-hackers@postgreSQL.org;
> Brian E Gallew; The Hermit Hacker
> Subject:	Re: [HACKERS] CORBA STATUS
	[Peter Mount]  [snip]
>  
> May be it is better make directory CORBA under interfaces subtree
> and time-to-time put objects for differend ORB's inside, 
> into separate directory.
> 
> Probably, It's better to make separate configure for 
> some parts of postgres distributions to allow users to build/upgrade
> parts of postgres i.e psql or perl interface 
> 
> 
> 
> 
> ---
> Dmitry Samersoff, dms@wplus.net, ICQ:3161705
> http://devnull.wplus.net
> * There will come soft rains ...
> 
> ************



From scrappy@hub.org Tue Nov  9 21:40:55 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
	by hub.org (8.9.3/8.9.3) with ESMTP id QAA01687;
	Tue, 9 Nov 1999 16:40:55 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id RAA44089;
	Tue, 9 Nov 1999 17:39:24 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Tue, 9 Nov 1999 17:39:20 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: phd2@earthling.net
cc: PostgreSQL-development <pgsql-hackers@postgresql.org>,
	pgsql-interfaces@postgresql.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <Pine.LNX.4.20.9911091822550.31442-100000@fep132.fep.ru>
Message-ID: <Pine.BSF.4.10.9911091624530.2296-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Whomever does this implementation, or works on this, needs to bear in mind
that there are several different ORBs out there, and the code should be
written in such a way that *I* can use MICO, Oleg here can use Fnorb,
someone  else can use ORBit, etc...I personally don't want to have to go
ut and grab <INSERT ORB of the Day here> just so that I can use CORBA,
when I already have Mico installed for other software...


On Tue, 9 Nov 1999, Oleg Broytmann wrote:

> On Tue, 9 Nov 1999, Dmitry Samersoff wrote:
> > > Anyway, I know that at least one ORB, TAO, runs on many more types of
> > > platforms than Postgres does (e.g. VxWorks, Lynx, Solaris, NT, ...),
> > > though Postgres runs on more Unix-style platforms. But that particular
> > > ORB is not a good candidate for us, for reasons I already mentioned
> > > (C++, large build size, poor configure support).
> > 
> > IMHO, There has no ideal ORB for all platforms.
> > we use ORBacus (http://www.ooc.com), 
> > because it's the only known for me ORB, working without threads 
> > so its really faster and more stable than another ones under FreeBSD,
> > but it's not free.
> 
>    FNORB - http://www.dstc.edu.au/Products/Fnorb/
>    Fnorb is a CORBA 2.0 ORB written in Python. Free for non-commercial
> use.
> 
> Oleg.
> ---- 
>     Oleg Broytmann     http://members.xoom.com/phd2/     phd2@earthling.net
>            Programmers don't die, they just GOSUB without RETURN.
> 
> 
> ************
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




From lockhart@alumni.caltech.edu Wed Nov  10 02:54:43 1999
Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204])
	by hub.org (8.9.3/8.9.3) with ESMTP id VAA50911;
	Tue, 9 Nov 1999 21:54:43 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id DAA09286;
	Wed, 10 Nov 1999 03:01:59 GMT
Sender: lockhart@hub.org
Message-ID: <3828E027.39DF0921@alumni.caltech.edu>
Date: Wed, 10 Nov 1999 03:01:59 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911091624530.2296-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Whomever does this implementation, or works on this, needs to bear in mind
> that there are several different ORBs out there, and the code should be
> written in such a way that *I* can use MICO, Oleg here can use Fnorb,
> someone  else can use ORBit, etc...I personally don't want to have to go
> ut and grab <INSERT ORB of the Day here> just so that I can use CORBA,
> when I already have Mico installed for other software...

Then forget it. Corba implementations don't work this way (yet).

Sorry you're not interested...

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From scrappy@hub.org Wed Nov  10 04:08:41 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
	by hub.org (8.9.3/8.9.3) with ESMTP id XAA60403;
	Tue, 9 Nov 1999 23:08:41 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA46392;
	Wed, 10 Nov 1999 00:07:13 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 10 Nov 1999 00:07:13 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <3828E027.39DF0921@alumni.caltech.edu>
Message-ID: <Pine.BSF.4.10.9911100004530.2296-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Nov 1999, Thomas Lockhart wrote:

> > Whomever does this implementation, or works on this, needs to bear in mind
> > that there are several different ORBs out there, and the code should be
> > written in such a way that *I* can use MICO, Oleg here can use Fnorb,
> > someone  else can use ORBit, etc...I personally don't want to have to go
> > ut and grab <INSERT ORB of the Day here> just so that I can use CORBA,
> > when I already have Mico installed for other software...
> 
> Then forget it. Corba implementations don't work this way (yet).

Wait...when we talked about this months back, I swore that one of the
conclusions *was* that this was possible...it would involve us doing
wrapper functions in our code that were defined in an include file based
on which ORB implementation was used...?

Basically...

pg_<corba function> maps to <insert mico corba function here>
			 or <insert orbit corba function here>
		  	 or <insert other implementation function here>

Has this ability changed? *raised eyebrow*


Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




From lockhart@alumni.caltech.edu Wed Nov  10 04:18:35 1999
Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204])
	by hub.org (8.9.3/8.9.3) with ESMTP id XAA61957;
	Tue, 9 Nov 1999 23:18:35 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id EAA09742;
	Wed, 10 Nov 1999 04:25:27 GMT
Sender: lockhart@hub.org
Message-ID: <3828F3B7.E17400D3@alumni.caltech.edu>
Date: Wed, 10 Nov 1999 04:25:27 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911100004530.2296-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> Wait...when we talked about this months back, I swore that one of the
> conclusions *was* that this was possible...it would involve us doing
> wrapper functions in our code that were defined in an include file based
> on which ORB implementation was used...?
> Basically...
> pg_<corba function> maps to <insert mico corba function here>
>                          or <insert orbit corba function here>
>                          or <insert other implementation function here>
> Has this ability changed? *raised eyebrow*

No, this probably is not necessary since the C or C++ mappings for
function calls in Corba are very well defined. 

What is not fully specified in the Corba standard is, for example,
which header files (and by what names) will be generated by the IDL
stubber, so each Orb has, or might have, different conventions for
include files. This probably impacts server-side code a bit more than
clients.

There is some interest for some Orbs to try lining up the header file
names, but I don't know how feasible it is in the short term.

We could probably isolate this into Postgres-specific header files,
but there will probably be Orb-specific #ifdef blocks in those
headers.

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From Michael.Ansley@intec.co.za Wed Nov  10 07:21:04 1999
Received: from s-nath-exch1.nath-gpbry.co.za (mail.newaftech.com
	[209.212.104.161]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA89080;
	Wed, 10 Nov 1999 02:21:04 -0500 (EST)
	(envelope-from Michael.Ansley@intec.co.za)
Received: by S-NATH-EXCH1 with Internet Mail Service (5.5.2448.0)
	id <WBHH0NG6>; Wed, 10 Nov 1999 09:19:39 +0200
Message-ID: <1BF7C7482189D211B03F00805F8527F748C233@S-NATH-EXCH2>
From: "Ansley, Michael" <Michael.Ansley@intec.co.za>
To: "'Thomas Lockhart'" <lockhart@alumni.caltech.edu>, The Hermit Hacker
	<scrappy@hub.org>
Cc: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: RE: [INTERFACES] Re: [HACKERS] CORBA STATUS
Date: Wed, 10 Nov 1999 09:15:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"

Surely with autoconf, this becomes less of an issue.  I mean, if this is the
only major problem (which it likely isn't, but anyway), then the whole
exercise shouldn't be that hard.

MikeA

>> -----Original Message-----
>> From: Thomas Lockhart [mailto:lockhart@alumni.caltech.edu]
>> Sent: Wednesday, November 10, 1999 6:25 AM
>> To: The Hermit Hacker
>> Cc: phd2@earthling.net; PostgreSQL-development;
>> pgsql-interfaces@postgreSQL.org
>> Subject: [INTERFACES] Re: [HACKERS] CORBA STATUS
>> 
>> 
>> > Wait...when we talked about this months back, I swore that 
>> one of the
>> > conclusions *was* that this was possible...it would 
>> involve us doing
>> > wrapper functions in our code that were defined in an 
>> include file based
>> > on which ORB implementation was used...?
>> > Basically...
>> > pg_<corba function> maps to <insert mico corba function here>
>> >                          or <insert orbit corba function here>
>> >                          or <insert other implementation 
>> function here>
>> > Has this ability changed? *raised eyebrow*
>> 
>> No, this probably is not necessary since the C or C++ mappings for
>> function calls in Corba are very well defined. 
>> 
>> What is not fully specified in the Corba standard is, for example,
>> which header files (and by what names) will be generated by the IDL
>> stubber, so each Orb has, or might have, different conventions for
>> include files. This probably impacts server-side code a bit more than
>> clients.
>> 
>> There is some interest for some Orbs to try lining up the header file
>> names, but I don't know how feasible it is in the short term.
>> 
>> We could probably isolate this into Postgres-specific header files,
>> but there will probably be Orb-specific #ifdef blocks in those
>> headers.
>> 
>>                     - Thomas
>> 
>> -- 
>> Thomas Lockhart				
>> lockhart@alumni.caltech.edu
>> South Pasadena, California
>> 
>> ************
>> 



From vev@michvhf.com Wed Nov  10 11:22:44 1999
Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12])
	by hub.org (8.9.3/8.9.3) with SMTP id GAA30635
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 10 Nov 1999 06:22:44 -0500 (EST) (envelope-from vev@michvhf.com)
Received: (qmail 1400 invoked by uid 1001); 10 Nov 1999 11:22:45 -0000
Date: Wed, 10 Nov 1999 06:22:45 -0500 (EST)
From: Vince Vielhaber <vev@michvhf.com>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: The Hermit Hacker <scrappy@hub.org>, phd2@earthling.net,
	PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <3828F3B7.E17400D3@alumni.caltech.edu>
Message-ID: <Pine.BSF.4.05.9911100620490.1288-100000@paprika.michvhf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Nov 1999, Thomas Lockhart wrote:

> > Wait...when we talked about this months back, I swore that one of the
> > conclusions *was* that this was possible...it would involve us doing
> > wrapper functions in our code that were defined in an include file based
> > on which ORB implementation was used...?
> > Basically...
> > pg_<corba function> maps to <insert mico corba function here>
> >                          or <insert orbit corba function here>
> >                          or <insert other implementation function here>
> > Has this ability changed? *raised eyebrow*
> 
> No, this probably is not necessary since the C or C++ mappings for
> function calls in Corba are very well defined. 
> 
> What is not fully specified in the Corba standard is, for example,
> which header files (and by what names) will be generated by the IDL
> stubber, so each Orb has, or might have, different conventions for
> include files. This probably impacts server-side code a bit more than
> clients.
> 
> There is some interest for some Orbs to try lining up the header file
> names, but I don't know how feasible it is in the short term.
> 
> We could probably isolate this into Postgres-specific header files,
> but there will probably be Orb-specific #ifdef blocks in those
> headers.

Is there any reason configure couldn't handle this?

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH   email: vev@michvhf.com   flame-mail: /dev/null
  # include <std/disclaimers.h>       Have you seen http://www.pop4.net?
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================






From scrappy@hub.org Wed Nov  10 14:58:14 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA56552;
	Wed, 10 Nov 1999 09:58:14 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA50615;
	Wed, 10 Nov 1999 10:58:12 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 10 Nov 1999 10:58:12 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
cc: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <3828F3B7.E17400D3@alumni.caltech.edu>
Message-ID: <Pine.BSF.4.10.9911101056460.2296-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Nov 1999, Thomas Lockhart wrote:

> > Wait...when we talked about this months back, I swore that one of the
> > conclusions *was* that this was possible...it would involve us doing
> > wrapper functions in our code that were defined in an include file based
> > on which ORB implementation was used...?
> > Basically...
> > pg_<corba function> maps to <insert mico corba function here>
> >                          or <insert orbit corba function here>
> >                          or <insert other implementation function here>
> > Has this ability changed? *raised eyebrow*
> 
> No, this probably is not necessary since the C or C++ mappings for
> function calls in Corba are very well defined. 
> 
> What is not fully specified in the Corba standard is, for example,
> which header files (and by what names) will be generated by the IDL
> stubber, so each Orb has, or might have, different conventions for
> include files. This probably impacts server-side code a bit more than
> clients.
> 
> There is some interest for some Orbs to try lining up the header file
> names, but I don't know how feasible it is in the short term.
> 
> We could probably isolate this into Postgres-specific header files,
> but there will probably be Orb-specific #ifdef blocks in those
> headers.

Right, which is something that I thought we had pseudo-agreed upon the
last time through, that we woudl most likely require this...hadn't
realized it was for 'Orb-header files', but, IMHO, that's no worse then
putting in HAVE_MICO vs HAVE_ORBIT blocks and having it a configure
option...

See...I am interested, just not interested in having us tied to one
"vendor"...:)

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




From scrappy@hub.org Wed Nov  10 14:58:39 1999
Received: from thelab.hub.org (nat198.58.mpoweredpc.net [142.177.198.58])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA56606;
	Wed, 10 Nov 1999 09:58:39 -0500 (EST) (envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA50619;
	Wed, 10 Nov 1999 10:58:47 -0400 (AST) (envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Wed, 10 Nov 1999 10:58:47 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Vince Vielhaber <vev@michvhf.com>
cc: Thomas Lockhart <lockhart@alumni.caltech.edu>, phd2@earthling.net,
	PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
In-Reply-To: <Pine.BSF.4.05.9911100620490.1288-100000@paprika.michvhf.com>
Message-ID: <Pine.BSF.4.10.9911101058240.2296-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 10 Nov 1999, Vince Vielhaber wrote:

> On Wed, 10 Nov 1999, Thomas Lockhart wrote:
> 
> > > Wait...when we talked about this months back, I swore that one of the
> > > conclusions *was* that this was possible...it would involve us doing
> > > wrapper functions in our code that were defined in an include file based
> > > on which ORB implementation was used...?
> > > Basically...
> > > pg_<corba function> maps to <insert mico corba function here>
> > >                          or <insert orbit corba function here>
> > >                          or <insert other implementation function here>
> > > Has this ability changed? *raised eyebrow*
> > 
> > No, this probably is not necessary since the C or C++ mappings for
> > function calls in Corba are very well defined. 
> > 
> > What is not fully specified in the Corba standard is, for example,
> > which header files (and by what names) will be generated by the IDL
> > stubber, so each Orb has, or might have, different conventions for
> > include files. This probably impacts server-side code a bit more than
> > clients.
> > 
> > There is some interest for some Orbs to try lining up the header file
> > names, but I don't know how feasible it is in the short term.
> > 
> > We could probably isolate this into Postgres-specific header files,
> > but there will probably be Orb-specific #ifdef blocks in those
> > headers.
> 
> Is there any reason configure couldn't handle this?

As simple as a '--with-corba=mico' configure option ... or, I would think?


Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 




From olly@lfix.co.uk Wed Nov  10 15:43:05 1999
Received: from mail.enterprise.net (mail.enterprise.net [194.72.192.18])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA64345;
	Wed, 10 Nov 1999 10:43:05 -0500 (EST) (envelope-from olly@lfix.co.uk)
Received: from linda.lfix.co.uk (root@max04-063.enterprise.net
	[194.72.196.183])
	by mail.enterprise.net (8.8.5/8.8.5) with ESMTP id PAA02402;
	Wed, 10 Nov 1999 15:43:03 GMT
Received: from lfix.co.uk (olly@localhost [127.0.0.1])
	by linda.lfix.co.uk (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id PAA05115;
	Wed, 10 Nov 1999 15:42:54 GMT
Message-Id: <199911101542.PAA05115@linda.lfix.co.uk>
X-Authentication-Warning: linda.lfix.co.uk: Host olly@localhost [127.0.0.1]
	claimed to be lfix.co.uk
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
X-URL: http://www.lfix.co.uk/oliver
X-face: 
 "xUFVDj+ZJtL_IbURmI}!~xAyPC"Mrk=MkAm&tPQnNq(FWxv49R}\>0oI8VM?O2VY+N7@F-
	KMLl*!h}B)u@TW|B}6<X<J|}QsVlTi:RA:O7Abc(@D2Y/"J\S,
	b1!<&<B/J}b.Ii9@B]H6V!+#sE0Q
	_+=`K$5TI|4I0-=Cp%pt~L#QYydO'iBXR~\tT?uftep9n9AF`@SzTwsw6uqJ}pL,
	h(cZi}T#PB"#!k
	p^e=Z.K~fuw$l?]lUV)?R]U}l; f*~Ol)#fpKR)Yt}XOr6BI\_Jjr0!@GMnpCTnTym4f; c{;
	Ms=0{`D Lq9MO6{wj%s-*N"G,g
To: The Hermit Hacker <scrappy@hub.org>
cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS 
In-reply-to: Message from The Hermit Hacker <scrappy@hub.org> of Wed,
	10 Nov 1999 10:58:47 -0400.
	<Pine.BSF.4.10.9911101058240.2296-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 10 Nov 1999 15:42:53 +0000
From: "Oliver Elphick" <olly@lfix.co.uk>

The Hermit Hacker wrote:
  >> Is there any reason configure couldn't handle this?
  >
  >As simple as a '--with-corba=mico' configure option ... or, I would think?
 
>From the point of view of a package maintainer, I would much prefer a
solution that separated the choice of Orb from the main build.

If the choice goes into configure, I will have to pick a single Orb and
build the Debian package for that, or else make packages for every
Orb that Debian supports.  It would be better if I could build a generic
Orb-enabled PostgreSQL and produce a little pg-orb connection library
for each Debian-supported Orb.


-- 
      Vote against SPAM: http://www.politik-digital.de/spam/
                 ========================================
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
               PGP key from public servers; key ID 32B8FAA1
                 ========================================
     "But thanks be to God, which giveth us the victory 
      through our Lord Jesus Christ."     
                              I Corinthians 15:57 





From lockhart@alumni.caltech.edu Wed Nov  10 15:37:01 1999
Received: from localhost (IDENT:root@hectic-3.jpl.nasa.gov [128.149.68.205])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA63571;
	Wed, 10 Nov 1999 10:37:01 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id PAA10568;
	Wed, 10 Nov 1999 15:43:46 GMT
Sender: lockhart@hub.org
Message-ID: <382992B2.86C9C99F@alumni.caltech.edu>
Date: Wed, 10 Nov 1999 15:43:46 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: The Hermit Hacker <scrappy@hub.org>
CC: phd2@earthling.net, PostgreSQL-development <pgsql-hackers@postgreSQL.org>,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <Pine.BSF.4.10.9911101056460.2296-100000@thelab.hub.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> See...I am interested, just not interested in having us tied to one
> "vendor"...:)

I know. That still doesn't keep me from being in a bad mood after
spending 3.5 hours at the dentist yesterday :((

On the Corba fork vs thread issue:

It is true that the server process would need to be handed off to the
client in a different manner from the postmaster; with Corba you don't
just fork onto a different port and be done with it.

However, the postmaster *could* start up a server process and return
an IOR to the client, which givs the client a direct handle to the
server. The client would then initiate contact directly with the
server, and the postmaster is no longer involved.

afaik you could still fork in the postmaster, though whether our
streamlined tricks would work with every Orb is not certain. But that
is an optimization for our specific forking implementation, not a
fundamental feature.

As I mentioned, the real performance benefits come from having an
optimized query connection which bypasses the *expensive* string
conversions we currently use to pass data around.

                     - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From lamar.owen@wgcr.org Wed Nov  10 16:07:56 1999
Received: from www.wgcr.org (IDENT:root@www.wgcr.org [206.74.232.194])
	by hub.org (8.9.3/8.9.3) with ESMTP id LAA68637;
	Wed, 10 Nov 1999 11:07:56 -0500 (EST)
	(envelope-from lamar.owen@wgcr.org)
Received: from lorc.wgcr.org ([207.144.78.36])
	by www.wgcr.org (8.8.7/8.8.5) with SMTP id LAA13554;
	Wed, 10 Nov 1999 11:07:53 -0500
From: Lamar Owen <lamar.owen@wgcr.org>
Organization: Little to None
To: "Oliver Elphick" <olly@lfix.co.uk>, The Hermit Hacker <scrappy@hub.org>
Subject: Re: [HACKERS] CORBA STATUS
Date: Wed, 10 Nov 1999 10:57:51 -0500
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
Cc: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
References: <199911101542.PAA05115@linda.lfix.co.uk>
In-Reply-To: <199911101542.PAA05115@linda.lfix.co.uk>
MIME-Version: 1.0
Message-Id: <99111011093307.00555@lorc.wgcr.org>
Content-Transfer-Encoding: 8bit

On Wed, 10 Nov 1999, Oliver Elphick wrote:
> The Hermit Hacker wrote:
>   >> Is there any reason configure couldn't handle this?
>   >
>   >As simple as a '--with-corba=mico' configure option ... or, I would think?
>  
> From the point of view of a package maintainer, I would much prefer a
> solution that separated the choice of Orb from the main build.
> 
> If the choice goes into configure, I will have to pick a single Orb and
> build the Debian package for that, or else make packages for every
> Orb that Debian supports.  It would be better if I could build a generic
> Orb-enabled PostgreSQL and produce a little pg-orb connection library
> for each Debian-supported Orb.

The same issue is true for the RPM's -- which ORB?  If I'm on RedHat Linux, the
choice of ORB is going to depend upon the choice of desktops -- KDE or GNOME. 
ORBit is packaged standard for GNOME -- KDE 2 is going to use something else --
now, my understanding of CORBA is quite limited -- Thomas, you have far more
experience, as you are actively developing CORBA stuff.  If I choose to install
just KDE, KDE's ORB is going to be installed -- if I install GNOME, ORBit is
going to be installed. If I install both (the default), both ORB's will be
resident.

I can force the installation of a particular ORB through dependencies, but
that seems messy to me.

I CAN produce multiple sets of packages -- but that's going to cause all
manner of confusion for users.

Is it possible in the CORBA context to do what Oliver mentioned with a 'pg_orb'
abstraction layer to a generic CORBA-enabled postgreSQL??

It may seem like Oliver and I are getting the cart before the horse, but
the strategic decision of how to integrate CORBA into the system is going to
have wide-ranging repercussions for integrators.

 --
 Lamar Owen
WGCR Internet Radio
1 Peter 4:11



From lockhart@alumni.caltech.edu Wed Nov  10 17:16:49 1999
Received: from localhost (IDENT:root@hectic-3.jpl.nasa.gov [128.149.68.205])
	by hub.org (8.9.3/8.9.3) with ESMTP id MAA77960;
	Wed, 10 Nov 1999 12:16:49 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id RAA10800;
	Wed, 10 Nov 1999 17:23:47 GMT
Sender: lockhart@hub.org
Message-ID: <3829AA23.32852039@alumni.caltech.edu>
Date: Wed, 10 Nov 1999 17:23:47 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Lamar Owen <lamar.owen@wgcr.org>, The Hermit Hacker <scrappy@hub.org>
CC: Oliver Elphick <olly@lfix.co.uk>, pgsql-hackers@postgreSQL.org,
	pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] CORBA STATUS
References: <199911101542.PAA05115@linda.lfix.co.uk>
	<99111011093307.00555@lorc.wgcr.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> The same issue is true for the RPM's -- which ORB?  If I'm on RedHat Linux, the
> choice of ORB is going to depend upon the choice of desktops -- KDE or GNOME.
> ORBit is packaged standard for GNOME -- KDE 2 is going to use something else --
> now, my understanding of CORBA is quite limited -- Thomas, you have far more
> experience, as you are actively developing CORBA stuff.  If I choose to install
> just KDE, KDE's ORB is going to be installed -- if I install GNOME, ORBit is
> going to be installed. If I install both (the default), both ORB's will be
> resident.

Right.

> I can force the installation of a particular ORB through dependencies, but
> that seems messy to me.

Not so bad, but I understand your point.

> I CAN produce multiple sets of packages -- but that's going to cause all
> manner of confusion for users.

Right. Not worth the effort.

> Is it possible in the CORBA context to do what Oliver mentioned with a 'pg_orb'
> abstraction layer to a generic CORBA-enabled postgreSQL??

Maybe, as a second step. The first step (which we are a *long* ways
away from; getting a consensus on how to proceed will take a miracle)
will be to get an implementation using one Orb with the feature set we
want.

> It may seem like Oliver and I are getting the cart before the horse, but
> the strategic decision of how to integrate CORBA into the system is going to
> have wide-ranging repercussions for integrators.

This may not be what people want to hear, and may not be what turns
out, but imho and imle ("little experience" ;)...

Corba is really intended to allow clients and servers implemented with
different Orb products to interoperate transparently. It has very
carefully stayed away from over-specifying exactly *how* a particular
client or server would be implemented for a particular Orb.

The header file conventions, or lack thereof, is a good example of
this. I'm familiar with a couple of the C++ Orbs. Mico produces a
single header file per interface, while TAO produces two. Hmm, it just
dawned on me that I might be able to jigger the output file names from
TAO's IDL compiler to make the names line up with Mico. Will get back
to you on this detail :)

Anyway, if Corba is in our future, I would think that we would work
with a single Orb for the server-side implementation, at least at
first. Once we are up and running, then we talk about how to slip in
someone's favorite other Orb.

For clients, we will have to pick and choose depending on the language
and features required. For example, TAO has portability and some
realtime features and optimizations that make it the *only* choice for
our realtime systems at work. But Mico has a nice TCL binding, so we
are using that to implement some TCL GUIs for commanding and telemetry
interfaces.

Not a big deal, and we quickly got over the *flap arms all over* "Oh
no! This Orb doesn't support language X!!!!".

btw, the Orb which has more language bindings than any other is ILU.
ILU predates Corba by several years, but it has evolved to support the
Corba standard in many areas.

Corba was primarily intended to decouple clients from servers.
Inter-orb transportability at the source code level was a secondary
concern, though the Corba standard, or at least some of the
conventions used in the open-source implementations, may be converging
a bit to help with the source portability. And the biggest
source-level portability concern, the call-level interfaces, is not a
problem.

As we are introducing Corba to new users at work (we've got O(20)
programmers who will be using it on our testbeds and ground
implementations for optical interferometers), I emphasize the
following:

1) Corba makes distributed computing easy, in that clients (the
calling programs) call servers (the subroutines) as though they were
local to the client. But in fact they could reside anywhere.

2) Specifying interfaces through IDL is a *great* way to design
systems. If you have the interface, then you know what you need to
implement. From then on, clients and servers, or callers and call-ees,
can be implemented independently. If we end up with Corba in our
server, then we could/should start specifying our internal interfaces
with IDL also.

3) Since clients and servers are decoupled through well-defined
interfaces, and since these interfaces can be decoupled "on the wire",
you have great flexibility in how you mix and match Orb products to
implement clients and servers. But afaik all of the Orbs have a "short
circuit" which will allow you to build Corba-enabled routines written
with that Orb into the same image, without taking a hit at runtime to
marshall/unmarshall/network/etc.

One in an occasional series... ;)

                 - Thomas

btw, I'm guessing that the way to get Corba going is to have a code
freeze/fork, and have a few people work on demonstrating Corba using
that frozen version. Then we re-merge later if the Corba demo was a
success *and* if Corba is what we want in the main-line product. That
could happen during our 7.x series of releases, and if the world wants
Corba, we could mainstream it for v8.0.

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From brendan@w3s.ie Wed Nov  10 18:31:23 1999
Received: from ns.w3s.ie (www.w3s.ie [193.120.211.43])
	by hub.org (8.9.3/8.9.3) with ESMTP id NAA88080
	for <pgsql-interfaces@postgresql.org>;
	Wed, 10 Nov 1999 13:31:23 -0500 (EST) (envelope-from brendan@w3s.ie)
Received: from w3s.ie ([193.120.135.58])
	by ns.w3s.ie (8.9.3/8.9.3) with ESMTP id SAA07143
	for <pgsql-interfaces@postgresql.org>; Wed, 10 Nov 1999 18:29:47 GMT
Message-Id: <199911101829.SAA07143@ns.w3s.ie>
X-Mailer: exmh version 2.0.2
To: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Re: [HACKERS] CORBA STATUS 
In-Reply-To: Your message of "Wed, 10 Nov 1999 17:23:47 GMT."
	<3829AA23.32852039@alumni.caltech.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 10 Nov 1999 19:31:45 +0000
From: "Brendan McKenna" <brendan@w3s.ie>

Hi,

	A (possibly) simple solution to the problems people seem to be having 
with the variety of incompatibilities between the various ORBs out there 
might be to simply produce a version for whatever ORB you like -- but publish 
the IDL interfaces and let people know enough of the background information 
so that if they want to use a different ORB than the 'baseline' 
implementation, this is the interface that they have to code to.

	That way, -you- (whoever you are) who implement the PostgreSQL/CORBA 
interface can only do it for your ORB of choice, and others can make the 
appropriate interfaces for their ORBs -- and make them available for the rest 
of us, hopefully....


							Brendan
-- 
Brendan McKenna	
Technical Director			Phone: +353-(0)61-338177 x4143
W3 Services Ltd.			  Fax: +353-(0)61-338065
Innovation Centre			Email: brendan@w3s.ie
National Technological Park
Limerick
Ireland





From bruce@cenderis.demon.co.uk Wed Nov  10 23:37:50 1999
Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net
	[194.217.242.39]) by hub.org (8.9.3/8.9.3) with ESMTP id SAA37967;
	Wed, 10 Nov 1999 18:37:50 -0500 (EST)
	(envelope-from bruce@cenderis.demon.co.uk)
Received: from cenderis.demon.co.uk ([193.237.0.193])
	by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1)
	id 11lhJB-0004mb-0B; Wed, 10 Nov 1999 23:37:46 +0000
Received: by cenderis.demon.co.uk (Postfix, from userid 1000)
	id 2B7012A578; Wed, 10 Nov 1999 23:37:48 +0000 (GMT)
To: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] Re: [HACKERS] CORBA STATUS
References: <199911101542.PAA05115@linda.lfix.co.uk>
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Date: 10 Nov 1999 23:37:38 +0000
In-Reply-To: "Oliver Elphick"'s message of "Wed, 10 Nov 1999 15:42:53 +0000"
Message-ID: <87emdx7wal.fsf@cenderis.demon.co.uk>
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) XEmacs/21.2 (Shinjuku)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 18

"Oliver Elphick" <olly@lfix.co.uk> writes:

> From the point of view of a package maintainer, I would much prefer
> a solution that separated the choice of Orb from the main build.
> 
> If the choice goes into configure, I will have to pick a single Orb
> and build the Debian package for that, or else make packages for
> every Orb that Debian supports.  It would be better if I could build
> a generic Orb-enabled PostgreSQL and produce a little pg-orb
> connection library for each Debian-supported Orb.

It probably makes sense to try to get things working with one ORB, and
then see if it's worth generalising.  I'd guess ORBit is a good one to
start with since it's C-based, and it's pretty small: if I have to
install an extra package on my machine just to run PostgreSQL, I'm not
going to mind ORBit, whereas TAO might annoy me (IIRC, TAO is quite
big; I may be thinking of another ORB, though).  ORBit does IIOP, I
believe, so that covers GNOME and KDE people.



From lockhart@alumni.caltech.edu Thu Nov  11 15:29:29 1999
Received: from localhost (IDENT:root@hectic-4.jpl.nasa.gov [128.149.68.206])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA65554;
	Thu, 11 Nov 1999 10:29:29 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id PAA05333;
	Thu, 11 Nov 1999 15:35:58 GMT
Sender: lockhart@hub.org
Message-ID: <382AE25E.485114A@alumni.caltech.edu>
Date: Thu, 11 Nov 1999 15:35:58 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Stephens <bruce@cenderis.demon.co.uk>
CC: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: [HACKERS] CORBA STATUS
References: <199911101542.PAA05115@linda.lfix.co.uk>
	<87emdx7wal.fsf@cenderis.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> It probably makes sense to try to get things working with one ORB, and
> then see if it's worth generalising.  I'd guess ORBit is a good one to
> start with since it's C-based, and it's pretty small: if I have to
> install an extra package on my machine just to run PostgreSQL, I'm not
> going to mind ORBit, whereas TAO might annoy me (IIRC, TAO is quite
> big; I may be thinking of another ORB, though).  ORBit does IIOP, I
> believe, so that covers GNOME and KDE people.

Yeah, TAO might annoy you; it takes 1.3GB of disk space to build,
though much less once built ;)

                     - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



From christof.petig@wtal.de Tue Nov  30 07:34:14 1999
Received: from mail.kdt.de (mail.kdt.de [195.8.224.4])
	by hub.org (8.9.3/8.9.3) with ESMTP id CAA01210
	for <pgsql-hackers@postgresql.org>;
	Tue, 30 Nov 1999 02:34:14 -0500 (EST)
	(envelope-from christof.petig@wtal.de)
Received: from gateway.petig.de (line0352lf.kdt.de [195.8.240.102])
	by mail.kdt.de (8.8.8/8.8.8) with ESMTP id IAA32290;
	Tue, 30 Nov 1999 08:34:10 +0100
Received: from wtal.de (christof@[192.168.230.9])
	by gateway (8.8.8/8.8.8) with ESMTP id IAA19981;
	Tue, 30 Nov 1999 08:25:12 +0100
Sender: christof@to.wtal.de
Message-ID: <38435618.4A82449E@wtal.de>
Date: Tue, 30 Nov 1999 05:44:10 +0100
From: Christof Petig <christof.petig@wtal.de>
Organization: Adolf Petig GmbH. & Co. KG
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.7 i586)
X-Accept-Language: de
MIME-Version: 1.0
To: mail-list@molnir.com
CC: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] CORBA STATUS
References: <001401bf2a53$23d22510$dea993c3@tosh3>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by hub.org id CAB01522

Mark Proctor wrote:

>  I'm currently studying for a Masters at BrunelUniversity, London. I
> was looking for a thesis andsince I had an interest inOpensource
> development anddatabases I thought that I would like to work onPGsql.
> As I also had an interest in trying tounderstand CORBA and other
> related technologies itmade sense that I try and work on a project
> that tiesPGsql and CORBA together in some way.
>
> Marc G. Fournier and Bruce Momjian were contacted withregards to this
> and they seemed to think that therewas room for me to work on this,
> although at thisstage I hadn't gone through the mailing list.
>
> since then I've finally got PGsql up and working andI'm now embarking
> on understand how to system actualworks. I thought a good place to
> start with myresearch would be to go through the mailing lists totry
> and see the current status for development in thisarea. I did this for
> several hours trying to get thecurrent take on CORBA with regards to
> PGsql. It seemsthere was a lot of initial talk back in Nov 1998 onthe
> hackers list with the first thoughts of some sortof CORBA
> implementation. The conversation orientatedover 2 main areas; which
> ORB and implementationmethods, with some peoples offering to work on
> this.It was then suggested that the converstaion take placein the
> interfaces mailing list. I've since been oversome of this but find it
> very difficult to understandthe current status with regards to PGsql
> and CORBA.I've seen many references to people who have developed
> a project that allows them to work with PGsql viaCORBA, but non of
> this seems to be part of the mainproject or system. There is some
> reference to Micheal Robinsonworking on an implementation but again
> I'm not surehow this fits
> in-http://www.postgresql.org/mhonarc/pgsql-interfaces/1998-11/msg00090.html
>
> Is there room for me to work on this project in such away that it is
> adequate for my masters. If anyone isworking on this, or has a good
> knowledge of thecurrent status of the CORBA implementation for
> PGsqlcan you please let me know, so I can know whether toget started
> on this or not. The reference thread formy initial point of contact
> with Marc G. Fournier andBruce Momjian and how they think I should
> attack theproject is
> -http://www.postgresql.org/mhonarc/pgsql-hackers/1999-09/msg00076.html
>
> Regards
>
> Mark Proctor
> email : m.proctor@bigfoot.com

Dear Mark,

as this reply stuck between my brain and my fingers for two weeks now,
it might come too late.
But Corba defines a Facility (or a Service) to access object oriented
databases via a standardized interface. Since Postgres is an OORDBMS
(there is a definitely shorter abbreviation), it might suit it well to
offer such an interface. I never looked too deep into the standard
document but if you are interested, I'll look up the exact location.

Since this does not interfere with Postgres' internals it should be much
easier to do. And since a redesign (for speed) of the backend interface
would not provide new features, I would suggest taking a look into this
area.

IMHO the Corba specs should get more attention. I really like these
standardization efforts, though they rarely affect everyday (free)
programming environments.

Regards
  Christof
 (which was tempted to implement them some month ago but decided to
build actual programs on now-available and (to me) well known technology
(ecpg driven Corba objects)).