Fwd: "serialization" of ListeningPort

[Daira Hopwood]

On 22/07/14 17:25, David Stainton wrote:
> In this case the server needs to announce a client endpoint string
> to various clients... the server has enough information to construct
> the endpoint string after the listening port has been created. However
> the construction of the endpoint string is not done in an endpoint
> agnostic manner... and this code will therefore break when used with
> Unix domain socket endpoints for instance.
> 
> One way to accomplish endpoint agnosticism would be to have a global
> function called
> "getClientEndpointStringFromPort" or something like that. This
> function would take an IListeningPort object as it's only argument and
> return a client endpoint string which can be used to connect to that very
> listening port.

listeningPort.getEndpointDescription() would be a more elegant API, no?
But yes, I agree this would be useful, however the API is spelled.

-- 
Daira Hopwood ⚥

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20140729/090b86b2/attachment.pgp>