Hi Garrette,
I suppose you mean :
Note that soon these raw mode sockets will be something that *very FEW*
people will need…
on the python/ruby binding I guess that people would love to use
this ‘context’
to get a binding to a ‘closure’ near to their code along with native ‘call
back’
function in their own eco-system and that ‘legacy’ and ‘raw’ could be
used in C or more bare metal environments/needs.
On Wed, Apr 4, 2018 at 9:59 PM, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:
I’m about to change the API for raw mode, as was discussed here. This
affects NNG users who are using the “new” API. (The legacy API is
unaffected.)
Previously, raw mode was selected via a socket option (NNG_OPT_RAW).
After integrating #331, this will no longer be a writable option, but
instead you will need to use a different protocol-specific constructor if
you need raw mode sockets. These are the same as the normal constructors,
but with the suffix “_raw” added, for example “nng_req0_open_raw()”.
Note that soon these raw mode sockets will be something that *very* people
will need, as I’m nearly ready to also push the separate context support
that should make concurrent cooked mode uses *much* nicer. (I’m working on
that in a branch and am nearly ready.)
This change will be in the next tagged release, which you can expect in
the next day or two.
- Garrett
