Actually, after thinking about it a bit more, I've decided to change to
a better design and require each calling app to ask for their own
ILayerManager which will create a unique TAutoIntfObject for them. They
then use that layer manager to make the call to AddLayer etc.
As an added bonus, I have fewer threading concerns with it.
Phil.
Conor Boyd wrote:
I'd be interested to see if anybody comes up with one.
We've gone down the extra parameter route, and use that to locate some
client-specific state/context that we maintain on the server.
C.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Phil Middlemiss
Sent: Wednesday, 31 May 2006 10:17 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: [DUG] Apartment model - identifying calling process
I'm using the Apartment threading model for an out-of-process automation
object.
Say the automation object has a method called AddLayer - is there any
way, without requiring extra parameters to be passed, to identify which
process is calling that method? That is, are there any COM methods to
ask for an ID for the current caller using the COM object's thread?
Phil.
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
begin:vcard
fn:Phil Middlemiss
n:Middlemiss;Phil
org:Vision Software, MTS Ltd
email;internet:[EMAIL PROTECTED]
title:Project Leader
tel;work:+64 7 3480001
tel;cell:+64 27 4592648
x-mozilla-html:TRUE
url:http://www.tumonz.co.nz
version:2.1
end:vcard
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
