The simple comment is that a) do you always have control on how your
applications are to be deployed - for example, can you guarantee that your
apps won't be deployed using some other mechanism (such as MTS or COM+) and
b) do you really want to tie in some mechanism that isn't supported and
frowned on with OLE when Microsoft has such a tendency to change things? I
just wouldn't do it - i'd find another way around the problem...
----- Original Message -----
From: "Myles Penlington" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Friday, June 16, 2000 12:46 PM
Subject: RE: [DUG]: COM types and pointers
> However if objects are created in the same apartment and same thread with
an
> Inprocess DLL only, I have always found them to be in the same
> process/thread space. Actually from the way I see this, this must always
be
> okay - as long as the COM objects reside in the same DLL and same
apartment,
> as the is nothing special in Delphi terms about the
> TAutoObjectFactory.CreateComObject call.
>
> For out of process or local servers this would always fail.
>
> Comments Richard?
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
