+1
On 30/03/16 11:25, Robbie Gemmell wrote:
Hello folks,
Many moons ago, a seperate mailing list was established for Proton,
back when it was purely a protocol engine other components would use.
Its scope has since expanded beyond that and the separate mailing list
has I feel been an
+1 on Alan's comments
Qpid has lots of components and a single cohesive user list as the
"entry point" is the best way to foster community IMHO.
F.
On 24/03/16 21:29, Alan Conway wrote:
On Thu, 2016-03-24 at 18:23 +, Troy Daniels wrote:
This was also the only mailing list that I found
Hello Sanny,
I know nothing about MQX OS so there is a limit to how much I can help you.
I ported proton to JavaScript which has similar complications, though
the workarounds are likely different.
Firstly the good news is that pipe() is only actually used for
pn_messenger_interrupt() in
explodingly long, so if conversation
develops it might be best to split it up a bit - it was mainly a bit of
a brain dump for Alan and I got carried away :-D I've moved to the Qpid
user and proton lists now for maximum exposure.
On Fri, Feb 6, 2015 at 6:20 AM, Fraser Adams
fraser.ad
by just following the directions in the README.
--Rafael
Frase
On 31/01/15 15:37, Rafael Schloming wrote:
Any chance you could send me a copy of your proton.js so I can try on my
system?
--Rafael
On Sat, Jan 31, 2015 at 10:32 AM, Fraser Adams
fraser.ad...@blueyonder.co.uk wrote:
Hi again
Hi again Rafi,
As I'm on a roll today.
So I've just done:
cd build
make clean
rm CMakeCache.txt
cmake -DCMAKE_BUILD_TYPE=Debug ..
(which gives the message: JavaScript build type is Debug)
make
and when I did
./recv.js
and in another window
./send.js
I'm not seeing any issue:
[
https://issues.apache.org/jira/browse/PROTON-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299841#comment-14299841
]
Fraser Adams commented on PROTON-810:
-
Matteo, I've made the changes to the package
you could send me a copy of your proton.js so I can try on my
system?
--Rafael
On Sat, Jan 31, 2015 at 10:32 AM, Fraser Adams
fraser.ad...@blueyonder.co.uk wrote:
Hi again Rafi,
As I'm on a roll today.
So I've just done:
cd build
make clean
rm CMakeCache.txt
cmake -DCMAKE_BUILD_TYPE=Debug
Hey All,
I was planning on making some tweaks to the JavaScript binding - in
particular changing the package name from qpid-proton to
qpid-proton-messenger. I think that the latter is better because we'll
likely want qpid-proton-reactor IDC and it would be a bit bloaty to
put both APIs in one
Thanks for the heads up Rafi.
I'll take a look when I've got a moment, that's not actually something
I've noticed before.
TBH I'm *pretty sure* that when I was developing this stuff I'd have
done what you've done, so I'm a bit baffled but I've mostly been using
non Debug builds lately and
Fraser Adams created PROTON-813:
---
Summary: Pulling latest version of ws WebSocket library from npm
central breaks JavaScript bindings.
Key: PROTON-813
URL: https://issues.apache.org/jira/browse/PROTON-813
[
https://issues.apache.org/jira/browse/PROTON-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed PROTON-813.
---
Pulling latest version of ws WebSocket library from npm central breaks
JavaScript bindings
[
https://issues.apache.org/jira/browse/PROTON-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved PROTON-813.
-
Resolution: Fixed
Sorry - I should've raised this Jira *before* I fixed things for tracking
On 15/12/14 11:03, Robbie Gemmell wrote:
The Apache Qpid PMC have voted to grant commit rights to Dominic Evans in
recognition of his contributions to and involvement with Proton.
Welcome, Dominic!
Welcome indeed Dominic!
Fraser Adams created PROTON-774:
---
Summary: Fix warnings in log.c and url.c and re-enable -Werror
Key: PROTON-774
URL: https://issues.apache.org/jira/browse/PROTON-774
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved PROTON-774.
-
Resolution: Fixed
Fix warnings in log.c and url.c and re-enable -Werror
Hey all,
I've been tearing my hair out a bit trying to figure why I can't see the
relevant Python modules.
I build Proton on a clean Linux Mint 17 system (which is based on Ubuntu
14.04)
make all builds successfully and sudo make install installs the following:
fadams@zappa
Fraser Adams created PROTON-760:
---
Summary: Improve the JavaScript binding's internal Event loop and
add additional tests
Key: PROTON-760
URL: https://issues.apache.org/jira/browse/PROTON-760
Project
On 29/11/14 16:00, Dominic Evans wrote:
I'm looking forward to checking this out now it has dropped into master. It
was only when you recently posted on the mailing list about it that I knew
it was in development. Thanks for the instructions to get up and running
with it too.
Yeah I should
On Thu, 2014-11-20 at 14:10 -0500, Michael Goulish wrote:
I am using two processors, both Intel Xeon E5420 @ 2.50GHz with 6144
KB cache. (Letting the OS decide which processors to use for my two
processes.)
On that system, with the above credit scheme, the test is sustaining
throughput of
On 08/10/14 08:16, xavier wrote:
Hi Frase,
Thanks for your explanation, but here, my code:
In the requester:
char * corrId;
.
.
pn_bytes_t bytes = pn_bytes(correlationId.size(), corrId);
pn_atom_t id;
id.type = PN_STRING;
id.u.as_bytes = bytes;
pn_message_set_correlation_id(message,
On 08/10/14 18:49, Rafael Schloming wrote:
On Wed, Oct 8, 2014 at 1:30 PM, Fraser Adams fraser.ad...@blueyonder.co.uk
wrote:
On 08/10/14 08:16, xavier wrote:
Hi Frase,
Thanks for your explanation, but here, my code:
In the requester:
char * corrId;
.
.
pn_bytes_t bytes = pn_bytes
On 07/10/14 08:04, xavier wrote:
Hi all,
Thanks you for your reply, help?
So if I understand properly, to do that with messenger is not trivial??? But
I don't understand why, because with the pattern request/reply in
asynchronous mode, and with dedicated queue, we must have this feature.
isn't
On 03/10/14 12:34, Dominic Evans wrote:
Rafael Schloming-3 wrote
I've created 0.8 RC1 and posted it in the usual locations. The source can
be found here:
http://people.apache.org/~rhs/qpid-proton-0.8rc1/
I know it is a *very* minor issue, but just for tidyness could someone fix
PROTON-618
On 11/09/14 15:25, Dominic Evans wrote:
fadams wrote
What do you think of the approach that I've taken? My rationale for
compiling proton-c to JavaScript and using a thin (ish) binding layer
rather than doing a ground-up native JavaScript rewrite was primarily
about support. I figured that
Fraser Adams created PROTON-662:
---
Summary: decoder.c pn_decoder_decode_value has a test that won't
correctly execute.
Key: PROTON-662
URL: https://issues.apache.org/jira/browse/PROTON-662
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved PROTON-662.
-
Resolution: Fixed
Added the correct casting.
Now compiles cleanly on both gcc and Clang
On 05/09/14 02:33, Miguel da Rocha Correia Lima wrote:
Hi Proton Subscribers,
We are using proton qpid for some AMQP software architecture proof
of concept. The objective is
use proton as our standard AMQP message client to router, gateway and
interface with user domain
applications and
Hi Ernie,
Quick response as I'm just going to bed.
Subscribing is fine from a browser so if say you are connecting to a
broker you can happily do a receive with an address like say localhost
or whatever, but a browser can't really act as a server - you are
clearly trying to get your browser
Hi again Ernie,
I've just committed a few improvements.
In terms of debugging if you specify
cmake .. -DCMAKE_BUILD_TYPE=Debug
or
cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo
it will do a build with no JavaScript optimisations and no closure
compiler so any JavaScript errors will be a bit more
Hi Again Ernie,
I take it back, it *was* something you've done ;-p
Or rather it was something that you didn't do.
If you look at the last line of the original send.js it says:
tracker = messenger.put(message);
But your last line below says simply:
messenger.put(message);
The error is simply
Hi again Ernie,
There's no real reason why it shouldn't work in a browser except that I
haven't tried it in a while, it tends to be easier to try things out
using node.js and doing some more browser tests was on my TODO list :-)
The error Uncaught TypeError: Cannot read property 'fa' of null
Hey Ernie,
You did read what I put in my previous response about the JavaScript
bindings using a *WebSocket* transport didn't you?
send.js and recv.js won't talk *directly* to the C++ broker, however
I've included a simple WebSocket-TCP Socket proxy.
If you stand up proxy.js that should
Hi Ernie
. In that repository the
fadams-javascript-binding/proton-c/bindings/javascript/qpid-proton does NOT contain a
lib directory. It only contains the files: LICENSE package.json README.md
Yeah that's likely to be the root of your problem, without that lib
directory being in place the
Hi Ernie,
Firstly bear in mind that it's still a bit of a work in progress :-)
though it's getting pretty close to something I'd want to put onto the
main branch, mostly just tidying stuff up now and adding a few more
tests and examples.
That said it was working fine for me when I made the
[
https://issues.apache.org/jira/browse/PROTON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004965#comment-14004965
]
Fraser Adams commented on PROTON-436:
-
Aha - glad I spotted this Jiira, so I'm
On 15/05/14 13:28, Tomáš Šoltys wrote:
Hi all
I have slightly modified an example send.c file to send message
containing 1024 bytes.
Above will result in zero sized message on the receiver side.
Is this an intention or a bug?
Regards,
Tomáš Šoltys
I doubt there's a *deliberate* limit ;-) ,
Hi Ernie,
Messenger per se certainly supports this, the python binding introspects
the types accurately and I'm currently writing unit tests for my
JavaScript port to prove test the JavaScript introspection behaves
correctly too, so if you are seeing an issue it'll be with the Perl
binding
Fraser Adams created PROTON-570:
---
Summary: Missing Ruby gem dependencies result in a fatal error of
Proton build.
Key: PROTON-570
URL: https://issues.apache.org/jira/browse/PROTON-570
Project: Qpid
Fraser Adams created PROTON-569:
---
Summary: Initialise pipe file descriptors to -1 in messenger prior
to calling pn_pipe
Key: PROTON-569
URL: https://issues.apache.org/jira/browse/PROTON-569
Project
[
https://issues.apache.org/jira/browse/PROTON-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved PROTON-569.
-
Resolution: Fixed
Initialise pipe file descriptors to -1 in messenger prior to calling pn_pipe
I'm sure others with more detailed knowledge of the background would be
able to give a better answer, but in short I think the thing that you
need to bear in mind is that proton Messenger is a *Message* oriented
API as opposed to a *Connection* oriented API, so for example compare
the approach
[X] Yes, release 0.7 RC4 as 0.7 final
[ ] No, 0.7 RC4 as the following issues...
Regards,
Frase
I must admit that I thought that recv was always necessary for what you are
doing, am I not correct that the python version of recv has an option with no
parameter (the one that use use in your XXX block) where the documentation says
something like if no Message instance is passed to recv then
Sorry Justin, I was thinking of get in my last mail, though I think when I've
done consumers using messenger I call recv once during initialisation and then
call get to retrieve the actual messages.
I've never found the correct workflow to use especially obvious though and I've
largely made it
Sorry, me again -curse being on an iPad, if you try the msg.recv bit before
your while True loop block I.e. do it once during initialisation, the the work
should (probably) be enough during the loop
Sent from my iPad
On 16 Apr 2014, at 14:45, Justin Ross (JIRA) j...@apache.org wrote:
Justin
On 28/03/14 15:20, serega wrote:
Thanks for the explanation. Yes, I used recv client.
I had to also call pn_data_next(body) to make it work, so it looks like so
--
pn_data_t *body = pn_message_body(message);
Hello,
If you are using the recv client (which you look like you are using)
then I *think* that what you are seeing is an artefact of that using
pn_data_format, which generates a *formatted* response. I think that's
because recv is intended to be a fairly general test client - when I
sent a
Fraser Adams created PROTON-535:
---
Summary: make docs results in several warnings and an error
Key: PROTON-535
URL: https://issues.apache.org/jira/browse/PROTON-535
Project: Qpid Proton
Issue
architectures).
Consequently the original patch which restricts va_arg processing to
simple types seems to me the most robust and portable solution. I
will proceed with that for 0.7.
Cliff
a bit indicates to me that clang is not somehow confused about
On Thu, Feb 27, 2014 at 9:01 AM, Fraser Adams
28, 2014 at 11:29 AM, Fraser Adams
fraser.ad...@blueyonder.co.uk wrote:
Hi, me again Cliff.
I've only had time to recheck this against my test case, which is
representative of what I see for real.
Doing:
int pn_data_vfill2(const char *fmt, va_list ap)
{
// Process the PROPERTIES constant
Starting from scratch is definitely the safest bet, but I *thought* that
you could just delete the CMakeCache.txt
Frase
On 05/02/14 18:53, Ted Ross wrote:
There's one other thing to be careful of... Once CMake determines
that it's not there, it will not reconsider after you've installed the
[
https://issues.apache.org/jira/browse/PROTON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883314#comment-13883314
]
Fraser Adams commented on PROTON-488:
-
Oh to be clear
either struct in and out
[
https://issues.apache.org/jira/browse/PROTON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883328#comment-13883328
]
Fraser Adams commented on PROTON-488:
-
For info I managed to pull out the bits
[
https://issues.apache.org/jira/browse/PROTON-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13883472#comment-13883472
]
Fraser Adams commented on PROTON-488:
-
Hey Cliff,
Re can you test if the review board
Out of curiosity which version of Proton are you using? I *think* that's
a fairly recent fix.
I was seeing something similar in my asynchronous experiments (I needed
to figure out when the message actually reached the receiver so I could
hold off terminating my async producer until then) and
Fraser Adams created PROTON-465:
---
Summary: FindPerlLibs.cmake module in Proton behaves differently
to Qpid's Perl detection
Key: PROTON-465
URL: https://issues.apache.org/jira/browse/PROTON-465
Project
[
https://issues.apache.org/jira/browse/PROTON-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated PROTON-465:
Assignee: Darryl L. Pierce
FindPerlLibs.cmake module in Proton behaves differently to Qpid's Perl
[
https://issues.apache.org/jira/browse/PROTON-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved PROTON-442.
-
Resolution: Fixed
Running swig generates Warning(451): Setting a const char * variable may
Fraser Adams created PROTON-442:
---
Summary: Running swig generates Warning(451): Setting a const
char * variable may leak memory.
Key: PROTON-442
URL: https://issues.apache.org/jira/browse/PROTON-442
60 matches
Mail list logo
