For a ServiceRegistrar implementation where you don't want to register
Services (A static ServiceRegistrar used only for lookup) would
returning a null ServiceRegistration suffice? Or is this fraught with
danger, has anyone ever tried it?
Use case: You've got an internet facing Registrar and you don't want
external Services to register.
Cheers,
Peter.
- Service API, class visibility, isolation and garbage col... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Dennis Reedy
- Re: Service API, class visibility, isolation and garbage... Gregg Wonderly
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Gregg Wonderly
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- ServiceRegistrar Peter Firmstone
- Re: ServiceRegistrar Tom Hobbs
- Re: ServiceRegistrar Patrick Wright
- RE: ServiceRegistrar Christopher Dolan
- Re: ServiceRegistrar Gregg Wonderly
- Re: ServiceRegistrar Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Peter Firmstone
- Re: Service API, class visibility, isolation and garbage... Dennis Reedy