search

SamCooper / COMMON_SPEC_RIDS

1 stars 0 forks source link

[Configuration Service] Use of the directory service #80

Closed ochurlaud closed 5 years ago

ochurlaud commented 6 years ago

The use of the directory service is not explicit in the specification. There is notably no such section as sections 3.4.4 and 3.4.6 which describe the use of the services Event and Archive.

However a service provider is identified in the API as a ServiceProvider COM object, which probably makes it mandatory for the service provider to register in the Directory service in order to be managed by the Configuration service.

This conflicts with another preliminary assertion in section 2.5:

It should be noted that the[re] is no direct relationship between the contents of the Directory service and the Configuration service. For example, there can be a different set of providers in an instance of the Directory service to that managed by an instance of the Configuration service. Basically, the Directory service is used to hold the address and the supported operations of providers whereas the Configuration service is used to hold the configuration of providers, however there is no requirement for these two sets of providers to be the same (although that may make sense in some deployments).

SamCooper commented 6 years ago

So, basically if there is no Directory Service how do I get my ServiceProvider COM objects?

lacourte commented 6 years ago

For the tests I allocate my own id and stores the ServiceProvider object in Archive. This would probably work in a real environment, as long as you let Archive allocate the id to avoid collisions.

SamCooper commented 6 years ago

Ok, so I can put in a comment indicating how it works when you don't have a directory service.

Would that be ok?

lacourte commented 6 years ago

Yes I think so

SamCooper commented 5 years ago

I have stated that the MO way of doing this is to use the Directory service to create them (i.e. they are shared), but that it is not a requirement. However if you do not link them then the mechanism for creating them is implementation specific.

I think for the tests it is probably best to either require them to already exist as part of the test scenario or add operation to a test service to create them.