For what it's worth, I like the explicit '*' because it's a pretty common
notation that I've seen used in many different places.
With this in mind, I feel like e.g. 'tcp://*:8888' is easier to understand than
is 'tcp://:8888' , especially for those who may be new to the library.
-Gilbert
________________________________
From: nanomsg-bounce@xxxxxxxxxxxxx <nanomsg-bounce@xxxxxxxxxxxxx> on behalf of
Garrett D'Amore <garrett@xxxxxxxxxx>
Sent: Friday, January 12, 2018 4:35:12 PM
To: nanomsg@xxxxxxxxxxxxx
Subject: [nanomsg] ditching the ‘*’ host wild card for websocket
For websocket (and perhaps also other transports?) I would like to eliminate
the special handling of the ‘*’ when specified as a host name. The reason is
that we already have an even shorter way to accomplish the same thing, which is
to simply omit the ‘*’ or hostname altogether.
For example, these are identical URIs:
ws:///somepath
ws://*/somepath
And also these are identical
tcp://:8888
tcp://*:8888
There seems little value or point to special casing the ‘*’ character, and I
plan to ditch it for the websocket transport at least (and probably all
transports) in nng.
(I will leave nanomsg alone, since some people are probably depending on this
URI format there.)
Any objections?
- Garrett
