[DUG] Apartment model - identifying calling process

[Phil Middlemiss]

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: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
> 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
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
>
>   
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phil.vcf
Type: text/x-vcard
Size: 250 bytes
Desc: not available
Url : http://ns3.123.co.nz/pipermail/delphi/attachments/20060531/0e0cd2a5/phil.vcf