On 14-11-12 03:57, Gregg Wonderly wrote:
Of course, the practical matter, is that in this day and age, server port numbers indicate specific types of services for the things in /etc/services. But, really, we should move the whole discovery business away from "socket creation parameters" and into a "mechanism" using an interface or abstract class so that through Configuration, it would be pluggable at deployment.
Not only this, but whe should create an abstract transport layer under jeri, with a bidirectional stream (similar to a socket). Communicating endpoints could be done with URI instead of serializing transport specific endpoints.
-- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
