Peter Donald wrote:
> At 03:44 PM 6/10/2002 +0200, you wrote:
>
>>> From what I understand from your description what I would suggest is
>>> that you do one of two things (in order of recomendation);
>>> 1. Write a utility that generated a set of metadata for set of
>>> metainfo objects that matched providers to required users etc.
>>> (Perhaps using attributes as hints to mapping).
>>
>>
>>
>> That's the prime objective - what you call "hint" is what I think of
>> as policy declarations. But aside from that, the immediate issue is
>> navigation. The associations I refered to above are built
>> progressivly - starting with a target component to execute, from
>> there, establishing the set of "potential" association, for each
>> potential association get its component info and from that component
>> info get it's potential associations, etc. etc.
>
>
> I get that but what I don't get is why you need back navigation. If
> you are always traversing down (which I believe you are?) then can't
> you just pass the associated ComponentInfo down? It only needs to go
> one level so you should be all good.
>
> If you need to go multiple levels anyway then I would suggest that you
> create a new metadata object anyways. So it will go
>
> metainfo -> intermediate -> metadata
>
> Besides putting backpointers would stop me reusing them directly in
> Phoenix ;)
Why?
The backpointers can be establihed in the ComponentInfo constructor -
totally transparent to Phoenix or any other client.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
