[
https://issues.apache.org/jira/browse/PROTON-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928803#comment-15928803
]
Andrew Stitcher commented on PROTON-1438:
-----------------------------------------
I'm not sure I like the
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=03ca9be change.
The newly allowed urls are not at all standard and it might be confusing to
people why they work for proton but not for any other purpose.
Addi5tionally, there is a good reason why the '['...']' notation is introduced:
For example, how should you interpret fe80::fc54:ff:feb8:6942? This is intended
to be [fe80::fc54:ff:feb8:6942]:5672 in all probability, but your code is going
to interpret this as [fe80::fc54:ff:feb8]:6942, which is likely to be
surprising and perhaps tricky to debug (as long hex strings that you cut and
pasted are not user friendly to scan).
> c proactor listening behavior
> -----------------------------
>
> Key: PROTON-1438
> URL: https://issues.apache.org/jira/browse/PROTON-1438
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: 0.17.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.18.0
>
>
> Improved listening behavior for pn_proactor_listen to allow selective
> listening by protocol (ipv4/v6) or portable "listen to everything".
> Host can be a host name, IPV4 or IPV6 literal,
> or the empty string/NULL (treated the same). The empty string listens on all
> local addresses. A host name listens on all addresses associated with the
> name. An IPV6 literal address (or wildcard '[::]') listens only for IPV6. An
> IPV4 literal address (or wildcard '0.0.0.0') listens only for IPV4.
> - pn_proactor_listen may listen on more than one socket for ipv6/v4 or
> for DNS names with multiple address records.
> - the 'backlog' applies to *each* socket (open for debate - we might
> want to divide the backlog among sockets with some minimum if there's
> not enough)
> - pn_listener_close() closes all sockets, PN_LISTENER_CLOSE event
> indicates all sockets are closed.
> - An error on any socket will close all the sockets of the listener,
> PN_LISTERN_CLOSE event indicates all sockets are closed and provides
> the error that triggered the close.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
