Hi Folks, I'm about to start working on the Carbon endpoint publisher. I had a look at the existing endpoint-publisher code and AFAIU this is how it works. The components registers an AxisObserver with the underlying AxisConfiguration. On service update event it gets the service EPR and writes it to a known location in the registry. The code needs some final touches and currently does not have a UI part. Before I get started on that I would like to know the actual requirements/expectations of the endpoint publisher component. What do we expect to achieve with this kind of functionality? Does writing all the endpoints to the registry sufficient for our requirements?
I also had a look at the WS-Discovery specs which is a standard way of discovering and publishing endpoints in a network. The protocol is multicast based. I believe some of the features we expect from the endpoint-publisher component can be done using WS-Discovery as well. So in the long run what should be our approach for discovering service endpoints? Thanks, Hiranya -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
