On Tue, 11 Jun 2002 22:52, Berin Loritsch wrote: > > From: Peter Donald [mailto:[EMAIL PROTECTED]] > > > > This is very very similar to what Stephen is doing in Merlin wrt to > > policies. ie Component A declares a dependency on Role P. If > > there is only > > one P in the system then that P will be used - however if > > there is multiple > > Ps in the system (namely x, y and z) then one of them will be > > selected > > based on a heuristic that takes a policy (aka a hint). > > > > The difference between Merlins model and the Cocoon model is > > that in Cocoon > > the metainfo (ie hint) is stored in code while in Merlin it > > is stored in > > descriptor (aka a .xinfo file). > > Another key difference is that the Cocoon model has a requirement > to re-connect the hint mappings at runtime--whereas the Merlin > model does it all at init time.
Can you explain that? You aquire components based on request parameters but the request parameters supply constraints and not hints (ie "ssl" vs "xalan"). -- Cheers, Peter Donald -------------------------------- These aren't the droids you're looking for. Move along. -------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
