qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1470) proactor api - flexible, parse-free addressing
Date Wed, 03 May 2017 02:22:04 GMT

    [ https://issues.apache.org/jira/browse/PROTON-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994175#comment-15994175
] 

ASF subversion and git services commented on PROTON-1470:
---------------------------------------------------------

Commit 4cf619cf58dd5b38309ae85f644e9cfb2600a025 in qpid-proton's branch refs/heads/master
from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=4cf619c ]

PROTON-1470: Add missing headers to source lists for tox tests

Added proton-internal.h and netaddr.h to source lists for tox tests


> proactor api - flexible, parse-free addressing
> ----------------------------------------------
>
>                 Key: PROTON-1470
>                 URL: https://issues.apache.org/jira/browse/PROTON-1470
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.17.0
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.18.0
>
>
> pn_proactor_connect and listen take a const char* string as the network address. This
creates ambiguity about what the string means. URLs are complex to parse and construct and
pn_url_t has been deprecated because it does not follow the URL standards well. Ad-hoc string
formats like "host:port" are confusing since IPv6 host addresses can contains ":" characters.
> Provide a simple pn_netaddr_t that can
> - provide a unquoted, separate host and port strings to connect and listen
> - inspect incoming addresses as standard struct sockaddr
> - get a readable, but not parsable, string from any network address
> - is extensible, in a binary compatible way, to support other address types for connect/listen
in future
> Note it is not a requirement (yet) to be able to connect/listen using an arbitrary sockaddr
but it should be possible to add such support in future in a source and binary compatible
way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message