Re: Sharing an ADO connection object between two processes ?
- From: "Brian Muth" <bmuth@xxxxxxxx>
- Date: Mon, 2 Oct 2006 08:51:04 -0700
"Herby" <prmarjoram@xxxxxxxxx> wrote in message
news:1159787801.059081.89760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have a client and server application that run on the same machine.
We want both to participate in the same transaction.
To acheive this I understand they need to share the same connection
object.
The server currently supports a COM interface, as the client passes
across copies of simple data types Strings and integers etc.
But now they want to pass across the client ADO connection object. The
data-writes within the server should then use this connection object
for creating its recordsets etc.
On return to the client - the client may then decide to commit or
rollback via the same connection object.
I understand the server would have a proxy back to the actual
connection object residing in the client address space. Is this going
to work?
Yes, it should work.... as long as the client and server run under the same
security context (ie. that they run as the same user).
It is very unusual to pass ADO connection objects across process boundaries.
I think a better way of managing transactions in this environment is to use
COM+. Develop an object (or objects) that house the particular transaction
logic and install it into COM+. The client then instantiates this object,
populates it with data, and then passes the interface to the server for
updating the database. Upon return the client can call one of the objects
methods to vote on the transaction.
HTH
Brian
.
- Follow-Ups:
- References:
- Prev by Date: Re: Random occurance of 0x8002801D (Re-phrasing the problem)
- Next by Date: Re: Sharing an ADO connection object between two processes ?
- Previous by thread: Sharing an ADO connection object between two processes ?
- Next by thread: Re: Sharing an ADO connection object between two processes ?
- Index(es):
Relevant Pages
|
|
