From: Taral <taral@cyberjunkie.com>
To: Hannu Krosing <hannu@trust.ee>
Cc: pgsql-hackers@hub.org
Cc: pgsql-interfaces@hub.org
Subject: CORBAservices (was RE: [HACKERS] PREPARE)
Date: Tue, 17 Nov 1998 12:21:52 -0600
Message-ID: <000c01be1257$2668a700$8a14f7d0@taral.dobiecenter.com> (raw)
In-Reply-To: <365130BC.FD2E87E2@trust.ee>
[ Cross-post to pgsql-interfaces ]
> BTW, what does CORBA prescribe about transactions (if anything) ?
>
> Is the current transaction model adequate or do we need nested
> transactions ?
The Query Service is read-only, so does not have locking or transactions...
We will have to implement the Transaction Service...
Current service list for our implementation: (in order of importance)
Naming Service (provided by most 2.2 ORBs)
LifeCycle Service (provided by mico) (dependent on NS)
Query Service
Security Service
ConcurrencyControl Service
Transaction Service (dependent on CCS)
Relationship Service (provided by mico)
(Not sure about the ordering of the last few...)
As you can see, this is a non-trivial list of interfaces :)
Taral
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: taral@cyberjunkie.com, hannu@trust.ee, pgsql-hackers@hub.org, pgsql-interfaces@hub.org
Subject: Re: CORBAservices (was RE: [HACKERS] PREPARE)
In-Reply-To: <000c01be1257$2668a700$8a14f7d0@taral.dobiecenter.com>
* 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