Re: Proton-c Null Messages
The strange thing is pn_messenger_get is returning 0, I have code to throw an error if it isn't 0. Also, the large messages work fine on RabbitMQ but not on Apache Apollo. -- View this message in context: http://qpid.2158936.n2.nabble.com/Proton-c-Null-Messages-tp7625967p7626075.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Re: Proton-c Null Messages
On Mon, Jun 08, 2015 at 05:56:14AM -0700, logty wrote: > Hi all, > > I just had a quick question about proton-c returning null messages. I am > calling pn_messenger_get on my message and on my messenger and getting back > messages that are null. When I call: > > pn_bytes_t b = pn_data_get_bytes(pn_message_body(message)); > > calls to b.start and b.size create segfaults. Any ideas as to why this might > be happening? At the moment I am running a test with large messages (several > megabytes) being sent to the server. > > Thanks for the help! Are you *certain* you're getting messages back? What's the return value on the call to pn_messenger_get? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpq1f55F5Ztp.pgp Description: PGP signature
[GitHub] qpid-proton pull request: Proton 781 ruby reactor apis
GitHub user mcpierce opened a pull request: https://github.com/apache/qpid-proton/pull/36 Proton 781 ruby reactor apis The Ruby Reactor APIs plus example applications. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/qpid-proton PROTON-781-ruby-reactor-apis Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/36.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #36 commit e77477b93b27a32eebc52dbde5c6793c5e6e42b6 Author: Darryl L. Pierce Date: 2015-02-23T21:18:01Z PROTON-781: Added the WrappedHandler class to the Ruby reactor APIs. commit 44d062c43979c2147a8c2ebe9d3e3c885c0b6869 Author: Darryl L. Pierce Date: 2015-02-23T21:19:33Z PROTON-781: Added the Task class to the Ruby reactor APIs. commit 4dffce64ff5f4e706043686fce781580322b7acb Author: Darryl L. Pierce Date: 2015-02-24T15:55:25Z PROTON-781: Deleted the Ruby Filter mixin. It was only used by Selectable, which is being refactored based on the new underlying C Selectable type. commit 9e8583c32c0e993643b012b2c42745ff30fc64cf Author: Darryl L. Pierce Date: 2015-02-24T18:31:51Z PROTON-781: Repackaged the Ruby Selectable class to Qpid::Proton. It's now a part of the core APIs and not part of the Messenger APIs. commit 9ff3e048d3f4a0af8bfa76806025f14b6f501f39 Author: Darryl L. Pierce Date: 2015-02-25T18:27:30Z PROTON-781: Added the Acking mixin to the Ruby reactive APIs. The Acking mixin provides methods for handling the settling of messages based on reactive callbacks. commit 43970df0cfc68f9acbc5458afffa9230c234885e Author: Darryl L. Pierce Date: 2015-02-25T18:28:38Z PROTON-781: Added EndpointStateHandler to the Ruby reactive APIs. commit b65cd5e1c7f1525d00226fe6332b1da4762e31e4 Author: Darryl L. Pierce Date: 2015-02-25T18:29:22Z PROTON-781: Added the CFlowController class to the Ruby reactive APIs. commit 3179116427fcac4c4ff24cbae1e70965b09d955f Author: Darryl L. Pierce Date: 2015-02-25T18:30:30Z PROTON-781: Added the BaseHandler class to the Ruby reactive APIs. This is the Ruby analog to the Handler class from Python. It needed to be renamed, though, since it's in the Qpid::Proton namespace but would collide with the Qpid::Proton::Handler namespace. commit 271b3a006927537545d899615150671b026e4c86 Author: Darryl L. Pierce Date: 2015-02-25T18:32:09Z PROTON-781: Added MessagingHandler to the Ruby reactive APIs. commit 498225e77c61aa3e9bf642c63b1c66d6cde47357 Author: Darryl L. Pierce Date: 2015-02-26T14:23:00Z PROTON-781: Added IncomingMessageHandler to the Ruby reactive APIs. commit 9eaa62ae275d619b0332af7da9f95f5298891d10 Author: Darryl L. Pierce Date: 2015-02-26T14:59:18Z PROTON-781: Added OutgoingMessageHandler to the Ruby reactive APIs. commit 340a9da719f1fcea1298d0dc71f40b4e641925a8 Author: Darryl L. Pierce Date: 2015-06-04T17:56:49Z PROTON-781: Refactored the Ruby Selectable class. It now more closely matches the Python version. commit 1573e5bf6744e6e016dc89ecc4dff264ed69f41e Author: Darryl L. Pierce Date: 2015-02-23T21:21:02Z PROTON-781: Added the Reactor class to the Ruby reactor APIs. commit b8ba5acb285d8f540dbf2226bb97cb564e8c09ff Author: Darryl L. Pierce Date: 2015-02-26T15:26:11Z PROTON-781: Added Container to the Ruby reactive APIs. commit cb84a677606a3265c73ec9ae07f3c96e964aa143 Author: Darryl L. Pierce Date: 2015-02-26T16:28:04Z PROTON-781: Added SSLConfig to the Ruby reactive APIs. commit 44f1312525c51a13ab6b82e1bff9050ec54297d2 Author: Darryl L. Pierce Date: 2015-02-26T16:28:35Z PROTON-781: Added GlobalOverrides to the Ruby reactive APIs. commit 0f45ba0f614438720cd16ba53d9e89e017b5779d Author: Darryl L. Pierce Date: 2015-02-27T15:14:57Z PROTON-781: Added Acceptor to the Ruby reactive APIs. commit 5b72338aee39379c56b799b6ec91aa2dbce3388f Author: Darryl L. Pierce Date: 2015-03-02T20:42:20Z PROTON-781: Added the Timeout mixin to the Ruby APIs. commit f69b9727f85768c07a46cd3759cc3c7bb342472c Author: Darryl L. Pierce Date: 2015-03-04T13:06:19Z PROTON-781: Added the Handler mixin to the Ruby reactive APIs. commit 953ba96fab906233a5522ce61881d7f5110375d1 Author: Darryl L. Pierce Date: 2015-03-04T15:54:54Z PROTON-781: Added Reactor and Task to the ClassWrapper commit 5504a7abca68cd303fc8273b438c5a08d9d1b36e Author: Darryl L. Pierce Date: 2015-03-04T21:36:39Z PROTON-781: Added the URL class to the Ruby core APIs. commit 5fc194adfea522fa36031f7648986e271357a7f7 Author: Darryl L. Pierce Date: 2015-03-04T21:37:12Z PROTON-781: Added the Reactor mixin to the Ruby reactive APIs. commit 4c09ae236bd0238a2444cd0237d7b001621a1c34 Author: Darryl L. Pierce Date:
Re: Proton-c Null Messages
After some research it appears to be a problem with messages over a certain size aren't being correctly sent/recieved and are instead being picked up by the messenger as null, although I don't know how to fix this, any thoughts? -- View this message in context: http://qpid.2158936.n2.nabble.com/Proton-c-Null-Messages-tp7625967p7626057.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
[jira] [Commented] (PROTON-781) Implement the Reactive APIs in Ruby
[ https://issues.apache.org/jira/browse/PROTON-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577582#comment-14577582 ] ASF subversion and git services commented on PROTON-781: Commit f63454c5caac0124f600793a96d9c560c15fa22f in qpid-proton's branch refs/heads/PROTON-781-ruby-reactor-apis from [~mcpierce] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f63454c ] PROTON-781: Reactive Ruby examples > Implement the Reactive APIs in Ruby > --- > > Key: PROTON-781 > URL: https://issues.apache.org/jira/browse/PROTON-781 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-781) Implement the Reactive APIs in Ruby
[ https://issues.apache.org/jira/browse/PROTON-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577580#comment-14577580 ] ASF subversion and git services commented on PROTON-781: Commit 3d94612780d5f299a2eb47cd54ddb488ff1360d4 in qpid-proton's branch refs/heads/PROTON-781-ruby-reactor-apis from [~mcpierce] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3d94612 ] PROTON-781: Added the set of LinkOption classes to Ruby. > Implement the Reactive APIs in Ruby > --- > > Key: PROTON-781 > URL: https://issues.apache.org/jira/browse/PROTON-781 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-781) Implement the Reactive APIs in Ruby
[ https://issues.apache.org/jira/browse/PROTON-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577579#comment-14577579 ] ASF subversion and git services commented on PROTON-781: Commit 9b30655f0dfefdc868989ff429b5d8b4395e6fea in qpid-proton's branch refs/heads/PROTON-781-ruby-reactor-apis from [~mcpierce] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9b30655 ] PROTON-781: Added support for reactors to the Ruby Endpoint class. > Implement the Reactive APIs in Ruby > --- > > Key: PROTON-781 > URL: https://issues.apache.org/jira/browse/PROTON-781 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-781) Implement the Reactive APIs in Ruby
[ https://issues.apache.org/jira/browse/PROTON-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577581#comment-14577581 ] ASF subversion and git services commented on PROTON-781: Commit 81c5cbd178141c959662a1c776a1df98556a90e0 in qpid-proton's branch refs/heads/PROTON-781-ruby-reactor-apis from [~mcpierce] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=81c5cbd ] PROTON-781: Ruby registry and memory management testing > Implement the Reactive APIs in Ruby > --- > > Key: PROTON-781 > URL: https://issues.apache.org/jira/browse/PROTON-781 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-781) Implement the Reactive APIs in Ruby
[ https://issues.apache.org/jira/browse/PROTON-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577578#comment-14577578 ] ASF subversion and git services commented on PROTON-781: Commit b8ba5acb285d8f540dbf2226bb97cb564e8c09ff in qpid-proton's branch refs/heads/PROTON-781-ruby-reactor-apis from [~mcpierce] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b8ba5ac ] PROTON-781: Added Container to the Ruby reactive APIs. > Implement the Reactive APIs in Ruby > --- > > Key: PROTON-781 > URL: https://issues.apache.org/jira/browse/PROTON-781 > Project: Qpid Proton > Issue Type: Improvement > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-895) Rely on python to build the downloaded tarball
[ https://issues.apache.org/jira/browse/PROTON-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577535#comment-14577535 ] ASF subversion and git services commented on PROTON-895: Commit e32f047c665686c827adb6a55f4f447c5d477644 in qpid-proton's branch refs/heads/master from [~kgiusti] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e32f047 ] PROTON-895: fix the Cyrus SASL check > Rely on python to build the downloaded tarball > -- > > Key: PROTON-895 > URL: https://issues.apache.org/jira/browse/PROTON-895 > Project: Qpid Proton > Issue Type: Bug >Reporter: Flavio Percoco >Assignee: Ken Giusti > Attachments: 0001-Rely-on-python-to-build-downloaded-tarball.patch > > > Recently, a patch that made python-qpid-proton's setup.py download proton-c > and build it whenever it's not found in the system. The patch relied on cmake > to build the library as everyone would do when building proton-c. > While that works, it's not the right, most pythonic, reliable way to do it. > Some reasons why it's not a good thing: > 1. It might overwrite a system qpid install if there's one and if the > python-qpid-proton library is being installed in the system > 2. It requires users - including CI systems, etc - to have cmake installed. > 3. It does everything from outside the Python mechanism. > The patch proposed in this bug changes the current behavior in favor of using > Python's build extensions to compile the library. The patch follows the same > steps as you'd do with cmake and it does it *just* for the downloaded > tarball. If there's an installed proton-c library, there's nothing to do. If > you're building it using cmake from a proton-c dir, it'll keep using cmake > normally. > The built library doesn't have the same name as the global one and it's > installed along with the python binding instead of installing header files > and the library itself system wide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-896) change all static function names to begin with pni_
[ https://issues.apache.org/jira/browse/PROTON-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael goulish reassigned PROTON-896: -- Assignee: michael goulish > change all static function names to begin with pni_ > --- > > Key: PROTON-896 > URL: https://issues.apache.org/jira/browse/PROTON-896 > Project: Qpid Proton > Issue Type: Improvement >Reporter: michael goulish >Assignee: michael goulish >Priority: Minor > > Change all the static function names to start with "pni_" , > and declare all functions as static that ought to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (PROTON-896) change all static function names to begin with pni_
[ https://issues.apache.org/jira/browse/PROTON-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] michael goulish closed PROTON-896. -- Resolution: Fixed commit d921c6bc8a05663daa2bc0ff38e6d8808b029802 > change all static function names to begin with pni_ > --- > > Key: PROTON-896 > URL: https://issues.apache.org/jira/browse/PROTON-896 > Project: Qpid Proton > Issue Type: Improvement >Reporter: michael goulish >Assignee: michael goulish >Priority: Minor > > Change all the static function names to start with "pni_" , > and declare all functions as static that ought to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-902: - Assignee: Ken Giusti > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco >Assignee: Ken Giusti > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: C++ versions for the C++ binding
On Mon, 2015-06-08 at 09:27 +0200, Tomáš Šoltys wrote: > Hi, > > since I need to compile proton on OpenVMS which does not support > C++11 nor > C++14 I would be more happy with C++03. > Thanks, I suspected there would be people out there :) So I'll go for plain ole C++03 to start with, if I add anything more recent it will be #ifdef'ed based on version. Cheers, Alan.
Re: has someone successfully built proton-c for iOS?
On Sun, 2015-06-07 at 21:28 -0700, yf wrote: > We are interested in using Proton-C library in an iOS app so that > data can be > sent to Qpidd server from iOS app. > > However, it seems that we can hardly find relevant materials for > using > Proton-C in an iOS app? We find some Proton introduction slides > mentioned > that proton-c is designed with portability in mind and iOS and > Android are > listed as the possible platforms to run Proton. > I'm not aware of anyone having done that yet, but proton was designed with portability in mind and should be able to run on iOS. Hopefully the folks on this list can help you out with any problems you find, and if you do write up the lessons you learn it would be a great addition to the proton documentation. Cheers, Alan.
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: (was: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch) > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch fixed an overflow issue > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-903) UUID version should be in sixth octet
[ https://issues.apache.org/jira/browse/PROTON-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-903: - Assignee: Gordon Sim (was: Ken Giusti) > UUID version should be in sixth octet > - > > Key: PROTON-903 > URL: https://issues.apache.org/jira/browse/PROTON-903 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco >Assignee: Gordon Sim > Attachments: > 0001-PROTON-903-Set-UUID-s-version-in-the-sixth-octet.patch > > > Python's UUID fallback implementation sets the UUID version in the seventh > octet instead of the sixth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-903) UUID version should be in sixth octet
[ https://issues.apache.org/jira/browse/PROTON-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti reassigned PROTON-903: - Assignee: Ken Giusti > UUID version should be in sixth octet > - > > Key: PROTON-903 > URL: https://issues.apache.org/jira/browse/PROTON-903 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco >Assignee: Ken Giusti > Attachments: > 0001-PROTON-903-Set-UUID-s-version-in-the-sixth-octet.patch > > > Python's UUID fallback implementation sets the UUID version in the seventh > octet instead of the sixth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-903) UUID version should be in sixth octet
[ https://issues.apache.org/jira/browse/PROTON-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577305#comment-14577305 ] Flavio Percoco commented on PROTON-903: --- reviewboard link: https://reviews.apache.org/r/35215/ > UUID version should be in sixth octet > - > > Key: PROTON-903 > URL: https://issues.apache.org/jira/browse/PROTON-903 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: > 0001-PROTON-903-Set-UUID-s-version-in-the-sixth-octet.patch > > > Python's UUID fallback implementation sets the UUID version in the seventh > octet instead of the sixth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-903) UUID version should be in sixth octet
[ https://issues.apache.org/jira/browse/PROTON-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-903: -- Attachment: 0001-PROTON-903-Set-UUID-s-version-in-the-sixth-octet.patch > UUID version should be in sixth octet > - > > Key: PROTON-903 > URL: https://issues.apache.org/jira/browse/PROTON-903 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: > 0001-PROTON-903-Set-UUID-s-version-in-the-sixth-octet.patch > > > Python's UUID fallback implementation sets the UUID version in the seventh > octet instead of the sixth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-903) UUID version should be in sixth octet
Flavio Percoco created PROTON-903: - Summary: UUID version should be in sixth octet Key: PROTON-903 URL: https://issues.apache.org/jira/browse/PROTON-903 Project: Qpid Proton Issue Type: Improvement Reporter: Flavio Percoco Python's UUID fallback implementation sets the UUID version in the seventh octet instead of the sixth. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577275#comment-14577275 ] Flavio Percoco commented on PROTON-902: --- Review board link: https://reviews.apache.org/r/35214/ > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch, > 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: (was: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch) > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: (was: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch) > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: (was: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch) > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-902) Make dependency on libuuid optional
[ https://issues.apache.org/jira/browse/PROTON-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Percoco updated PROTON-902: -- Attachment: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > Make dependency on libuuid optional > --- > > Key: PROTON-902 > URL: https://issues.apache.org/jira/browse/PROTON-902 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Flavio Percoco > Attachments: 0001-PROTON-902-Remove-the-dependency-on-uuid.patch > > > The current proton-c version depends on libuuid for, well, generating uuids. > The unfortunate thing of this dependency is that it's currently just required > by the messenger and it's just being used for building the messengers name. > It's really unfortunate to require this library and headers to be present for > such a small case. > It'd be possible to make this dependency optional by adding a built-in uuid4 > generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-902) Make dependency on libuuid optional
Flavio Percoco created PROTON-902: - Summary: Make dependency on libuuid optional Key: PROTON-902 URL: https://issues.apache.org/jira/browse/PROTON-902 Project: Qpid Proton Issue Type: Improvement Reporter: Flavio Percoco The current proton-c version depends on libuuid for, well, generating uuids. The unfortunate thing of this dependency is that it's currently just required by the messenger and it's just being used for building the messengers name. It's really unfortunate to require this library and headers to be present for such a small case. It'd be possible to make this dependency optional by adding a built-in uuid4 generator that'd be enabled whenever libuuid is not around. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-896) change all static function names to begin with pni_
[ https://issues.apache.org/jira/browse/PROTON-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577235#comment-14577235 ] ASF subversion and git services commented on PROTON-896: Commit d921c6bc8a05663daa2bc0ff38e6d8808b029802 in qpid-proton's branch refs/heads/master from Mick Goulish [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=d921c6b ] PROTON-896: declare functions static that are only referred to in one file, and change their names to have pni_ prefix. > change all static function names to begin with pni_ > --- > > Key: PROTON-896 > URL: https://issues.apache.org/jira/browse/PROTON-896 > Project: Qpid Proton > Issue Type: Improvement >Reporter: michael goulish >Priority: Minor > > Change all the static function names to start with "pni_" , > and declare all functions as static that ought to be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Proton-c Null Messages
Hi all, I just had a quick question about proton-c returning null messages. I am calling pn_messenger_get on my message and on my messenger and getting back messages that are null. When I call: pn_bytes_t b = pn_data_get_bytes(pn_message_body(message)); calls to b.start and b.size create segfaults. Any ideas as to why this might be happening? At the moment I am running a test with large messages (several megabytes) being sent to the server. Thanks for the help! -- View this message in context: http://qpid.2158936.n2.nabble.com/Proton-c-Null-Messages-tp7625967.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
has someone successfully built proton-c for iOS?
We are interested in using Proton-C library in an iOS app so that data can be sent to Qpidd server from iOS app. However, it seems that we can hardly find relevant materials for using Proton-C in an iOS app? We find some Proton introduction slides mentioned that proton-c is designed with portability in mind and iOS and Android are listed as the possible platforms to run Proton. Regards, yf -- View this message in context: http://qpid.2158936.n2.nabble.com/has-someone-successfully-built-proton-c-for-iOS-tp7625961.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
Re: C++ versions for the C++ binding
Hi, since I need to compile proton on OpenVMS which does not support C++11 nor C++14 I would be more happy with C++03. Regards, Tomas 2015-06-05 22:49 GMT+02:00 aconway : > I think this has been discussed before, but is there a consensus on > what C++ version we want to target for the C++ binding? C++03 is old > and smelly. C++11 is better, C++14 better still and afaik any compiler > that does 11 will do 14. So the sensible choices would seem to be: > > 1. Smelly C++03 code only > 2. C++03 compatible with #ifdef optional bits of C++14 niceness. > 3. C++14 first, add C++03 later if somebody whines about it. > > 3. is the most fun for me obviously. > > >
