I think that using "reference" rather than a protocol string is not a good idea, because it puts this important differentiation at the end rather than first. Just using
jini: for discovery V1 or V2 usb: for something over a USB interface of yet to be decided nature udt: for UDT mekong: for mekong etc., would be the right choice. For me, that would provide a better bases for a protocol handler/driver mechanism. Gregg Wonderly On Jan 5, 2013, at 3:03 AM, Peter Firmstone <[email protected]> wrote: > Gregg, > > Now you've got me thinking about Discovery v3 ;) > > replace hostname and port with a RFC3986 uri string. > > expand the URI format to allow other sockets, for example: > > * jini://hostname:port#IP - TCP/IP Socket > * jini://hostid#USB- USB Socket > * jini://hostname:port?socID=500#UDT - UDT Socket with socketID for > multiplexing 10x faster than TCP sockets and firewall friendly. > * jini://hostname:port#MEKONG - Sim? > > > replace SHA-1 hash functions with SHA-2 in |net.jini.discovery.ssl| format. > > Cheers, > > Peter. > >
