You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/09/06 14:49:20 UTC

[jira] [Updated] (QPID-6308) [C++ Messaging] Server example never sends utf8 responses

     [ https://issues.apache.org/jira/browse/QPID-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Ross updated QPID-6308:
------------------------------
    Fix Version/s: qpid-cpp-1.35.0

> [C++ Messaging] Server example never sends utf8 responses
> ---------------------------------------------------------
>
>                 Key: QPID-6308
>                 URL: https://issues.apache.org/jira/browse/QPID-6308
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Client
>    Affects Versions: 0.30
>         Environment: Qpid trunk on Fedora 19 Linux. 
> Running C++ Broker and C++ Messaging Server example.
> Amqp.Net Lite Client example
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>             Fix For: qpid-cpp-1.35.0
>
>
> Qpid C++ Messaging and Amqp.Net Lite have some issues interoperating.
> * Amqp.Net Lite encodes/decodes strings with binary encoding primitive 
> ** str8-utf8 0xA1
> * Qpid C++ Server decodes received str8-utf8 0xA1 strings ok but sends all replies with
> ** vbin8 0xA0
> * Qpid C++ Client always sends strings as
> ** vbin8 0xA0
> Modifying the Server example to:
> {noformat}
>     Message response;
>     response.setContentObject( request.getContentObject() );
>     sender.send(response);
> {noformat}
> preserves the str8-utf8 encoding in the response but doesn't process the message.
> The server example would be improved if it generated utf8 replies to utf8 requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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