Hello ICE-Dev, Scott,
I had pulled in the changes and looked at the video and wanted to clarify my understanding here:
1) The second instance of the Core, spawned from Core OSGi.launch is not visible since it needs endpoint discovery. This is supported through various ways:
EDEF: File format with information on how the consumer can find the host. Can import automatically or manually (for modifying certain properties).
Network discovery: Through zookeeper, zeroconf, etc.
Is EDEF preferred over Network discovery in specific cases?
I would think that EDEF doesn't rely on the existence of Network discovery protocols and so can be independent of that. However, Network discovery can publish the existence of a host, similar to a name server and thus does not need an explicit file to describe the endpoint.
2) Who would typically write the EDEF file, i.e. it looks like the Host is best placed to generate the endpoint information since it runs on the endpoint?
If the Host machine was to change frequently (say the consumer could connect to any machine in a cluster, each time it connected), would the EDEF file need to be updated each time? Would a network discovery approach be better here?
Hope I have described my doubts clearly. If you need any clarifications, please let me know.
Regards,
Ram
Hello Jay, Scott,
Thanks a lot for tackling various issues with regard to the OSGi services here. I got a chance to catch up on the conversation just about now. I will pull in the changes, focus on the EDEF file and will go through the uploaded video (thank you Jay) to understand what we have so far.
Regards,
Ram
