>>
>> To make any of this work we need to design an interface that the
>> domain provides for the runtime to work with. Has this process started
>> (I don't see anything obvious in the code base)? If not lets start a
>> discussion so we can coordinate activity.
>>
>> Simon
>>
>
> I don't think it exists yet either, so yes lets try come up with that
> interface. Do you have something in mind you could post or should i
> try to come up with a strawman?
>
> ...ant
>
What I would like to see is a simple registry style interface for
handling endpoint information, e.g.
public interface EndpointRegistry {
void addEndpoint(Endpoint2 endpoint);
void removeEndpoint(Endpoint2 endpoint);
void addEndpointReference(EndpointReference2 endpointReference);
void removeEndpointReference(EndpointReference2 endpointReference);
List<Endpoint2> findEndpoint(EndpointReference2 endpointReference);
List<EndpointReference2> findEndpointReference(Endpoint2 endpoint);
}
Two reasons, firstly we need to be able to ask the "domain" questions
about endpoints. Secondly I'm interested at the moment as we need to
understand how to ask endpoint resolution questions in order to finish
off the endpoint code. For example, one of the changes that is still
outstanding is support for serialization required by callable
references, this could help here also.
The 1.x domain manager provides a whole raft of "interfaces" already.
put/get contribution
put/get node configuration
put/get deployed composite (defines composite/node association)
get composite configuration for individual node
There are other things as well, e.g. there are file handling
interfaces, but not sure what it is for.
In the grand scheme of things we still need these but in many of our
scenarios I think we are expecting these interfaces to be called
automatically rather than manually though a web gui.
Simon
