Okay, sounds good. From experience with Blitz I would suggest a slightly different tack which is to leave RegistrarImpl as it is and expose some kind of Factory for creating such local lookups.
Reasoning: For a simple "make something local" exercise, slight tweaks to the service impl like making it public are enough. For more in depth stuff, as you're suggesting (and as done with Blitz's LocalSpace) there tends to be a lot more wiring and infrastructure that doesn't necessarily fit well inside of the core service impl. A factory makes it nice and easy to get what one is after whilst providing a layer of separation that affords a lot of flex in building exactly what's required. Cheers, Dan. <snip> > It is an environment, where you only have 1 vm started by webstart, no user > configuration, self determining config. Where i want to start a registry. I > want very little ports opened, to limit the users personal firewall > complaining (and causing worried support calls). Datacomm backbone costs are > high, mobile users with a local lan. No systems manager, enduser setup. > Webstart bulk download is primed before deployment in the field. > > > <snip> > And if possible, different timeouts on leases, determined by the type of > network interface. Short timeouts on lowcost paths long timeouts on highcost > paths. > > Gr. Sim >
