Verify that the registry->service instance APIs align with CF's definition about servicebroker HOT 6 CLOSED

add unit testcases too

from servicebroker.

Hey @duglin,

Can you clarify what you mean by service registry in this model?

from servicebroker.

I think you guys are using the term "service controller" - I mean the thing that keeps track of the list of available service brokers that are registered in the env. I can't bring myself to use the "controller" word :-) it just doesn't fit to me. In CF's case they use the term "cloud controller" because to them the CC is the brains(controller) of CF, but not just for the service registry piece of it. I think "service registry" is more descriptive to a newbie.

from servicebroker.

Ah okay, we have been using the term service registry as the name for the thing that stores service definitions (i.e., the thing that backs the service broker's catalog).

I think the controller is more than just a registry. In fact it doesn't really store a registry of anything because it's just aggregating from elsewhere, but it is controlling the injection of bindings into whatever context it runs in.

from servicebroker.

The entire "naming" issue is something I added to the agenda for the f2f - we need to get agreement just to avoid confusion. But in general, yes I mean the component that manages the list of registered services, and manages the list of service instances, and manages the list of service bindings, and injects them into the app.

I'm not sure we get into what's behind a service broker - that's an impl detail.

from servicebroker.

Sounds good, definitely worth having a unified vocab.

from servicebroker.