Hi, an issue concerning the URI: Right now, only the transport protocol is part of the URI (e.g. tcp:://...).
Shouldn't there be a hint to the application protocol, e.g. etch_tcp:://... which seems more appropriate? The question arises e.g. with the UDP extensions, which could provide different application semantics like "reliable_etch_udp" or "maybe_etch_udp". These protocols could use different headers, so it could be needed to distinguish between different application protocols in the URI. Best regards, Kay Weckemann BMW Group Research and Technology
