I like to use the socketpair(2) syscall for this, if you don't really need
a message broker.
--Albin
On Wed, May 29, 2019, 21:26 Brad Hein wrote:
> Packaging the json string as a vector of u8 integers worked like a charm,
> thank you for the suggestion!
>
> Python code:
> https://gist.github.co
Packaging the json string as a vector of u8 integers worked like a charm,
thank you for the suggestion!
Python code:
https://gist.github.com/regulatre/38e7162d6f470ad0dbd77b171a69dc79
C++ block code:
https://gist.github.com/regulatre/f264fb4751ca3bd8d6b98abf9792e95d
Memory consumption by the pyth
I'd recommend ZeroMQ; it's a pretty universally available socket
wrapper thing that is also "transport invariant", i.e. you can do
ZeroMQ "over the Internet" over classical TCP, just as much as for IPC
on the same machine. Unlike UDP, it can ensure messages actually reach
their target, and it's sup
Thanks for the clever insights, Marcus. I'll consider the PMT vector
approach you mentioned, while at the same time knowing PMT is likely to
undergo changes in the future as you mentioned, I'll also look into using
TCP/IP to pass the needed information, perhaps ZeroMQ or a UDP socket even.
On Fri,
Hi Brad,
so, yes, your observation is correct: PMT symbols are/were meant to be
used as "identifiers", not as "data carriers"; the motivation behind
the hash table you find in pmt.cc is that there's only one instance of
any given PMT symbol, and thus, a simple address comparison suffices to
tell w
In my gnuradio test application I’m attempting to pass a JSON formatted
string from my C++ custom block, to my python flow graph containing the
block.
The String message are being received by my python flow graph, but there’s
a memory leak. Over time, my flowgraph RSS (memory footprint) grows at
