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 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 CC: phd2@earthling.net, PostgreSQL-development , pgsql-interfaces@postgreSQL.org Subject: Re: [HACKERS] CORBA STATUS References: 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_ maps to > or > or > 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