Re: profile sharing and directory service

Conrad Carlen wrote:
> Judson Valeski wrote:
> 
>> Conrad Carlen wrote:
>>
>>> 2. The consumer could just explicitly ask for a non-shared location, 
>>> using the %ProcID% method I mentioned. This way, components have to 
>>> specify whether they use shared or non-shared data. I think that 
>>> localizes the control over what's shared to the component which uses 
>>> the data. Say that we are able to make the cache function with shared 
>>> data. Then we just change what location property *it* uses.
>>
>>
>>
>> I assume "ProcID" would actually be an "AppID" or something. ProcID 
>> implies variability (OS doesn't always give an app the same ProcID for 
>> example).
> 
> 
> Yes. "AppID" is a better term for it. Its value would always be constant 
> for a given executable between runs and reboots.

Wouldn't using (IP address, ProcessID) make more sense, since there may 
be multiple processes running simultanously that want to share a given 
dataset?

Dan