Dominic Tootell schrieb: > Thank you for that Reinhard, > That super class stuff answers another question I had :-) > > > What I have rather than inheritance is two actually two implementations. For > example: > > http://localhost:8888/recommendations?url=blah > http://localhost:8888/recommendations?rdf=blah > > > Under the hood these are actually two implementations of recommendations > engines that provide the same business functionality, but are implemented in > complete different ways (totally different code). Therefore, the code is > separate, and seems sensible to be in two separate blocks. But from a user > perspective, they don't want to know about the differences in implementation; > that just call /recommendations. Hence mapping the two blocks at one > mount-path. > > > I'll have a play around. > > Cheers, > /dom >
So actually your case is not "sharing resource" in the first place, but more combining existing sitemaps? Most easily you could create a "dispatcher" block that will divert to the correct implementations. (There will be new problems if some forms are involved, though) If the is a chance of a subtle change to the global namespace, such that the differentiating part is no longer an URL parameter but an URL part, using mount will be open again: In your above example this would probably look like: http://localhost:8888/recommendations/url/blah http://localhost:8888/recommendations/rdf/blah Then just mount one block to /recommendations/url the other one to /recommendations/rdf (Nevertheless, ths is a user visible change and probably only feasible if those URLs are generated somehow) Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
