Jean-Sebastien,
I've replied separately to your referenced note.
My suggestion is that resolution should be split from loading.
Resolution should take place in a cascade from the composites which are
at domain level, in response to explicit references discovered there.
Only entities in the actually deployed hierarchy will get resolved.
Mere presence of some entity in a contribution should be of no
significance for resolution. The problem today is that discovery and
resolution are tied together in the code.
This needs to look ahead to the point where specific entities in the
hierarchy of composition are not destined for the runtime node that is
performing the resolution.
Yours, Mike.
Jean-Sebastien Delfino wrote:
[snip]
Mike Edwards wrote:
Whether resolution occurs for all the resources simply depends on
whether there are resolvers for each type of resource.
+1 for improving this, did you see what I proposed in [1], and does it
make sense to you? Do you have any suggestions on how to implement this
lazy loading + resolution?
[1] http://www.mail-archive.com/[email protected]/msg18684.html
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
