[nanomsg] Re: NN_RCVPRIO option
- From: Garrett D'Amore <garrett@xxxxxxxxxx>
- To: nanomsg@xxxxxxxxxxxxx, Martin Sustrik <sustrik@xxxxxxxxxx>
- Date: Thu, 27 Mar 2014 08:12:40 -0700
Guess I’m going to have to add priorities to my Go implementation. For now
what I do is pretty simple/trivial. :-)
--
Garrett D'Amore
Sent with Airmail
On March 26, 2014 at 10:13:32 PM, Martin Sustrik (sustrik@xxxxxxxxxx) wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
There have been quite some discussion about NN_RCVPRIO socket option.
On one hand, it's an obvious counterpart to NN_SNDPRIO, on the other,
Paul Colomiets have done a good work arguing that we are missing use
cases for the option and thus we shouldn't expose it to the user.
I've been thinking about the option for some time already and finally
I've decided to include it into nanomsg API.
The rationale is that if client (e.g. REQ socket) is allowed to choose
which service provider to use preferentially, the service provider
(e.g. REP socket) should be allowed to choose which clients to serve
in preference.
The use cases span from freemium business model (serving free users
only after paying users have already been served) to processing
signals from the car's engine before signals from the entertainment
system in the automotive industry.
The option is already available in the trunk. Enjoy!
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTM7NvAAoJENTpVjxCNN9YIl0IAK83UAv5hWYegeVX8QzA82Fb
C4uNtNchvqg2rBLl8hQkY3Id1Fs009Efx/cA7n4bnjGjVLlIPr8D7bNdFKMq2vJo
RoQSR1XVtuC44UTSYkrZyeKIf7+/QtGCjLFhna1YT0cjNtA0paOHQYn/i2Tk8Phq
nONXu4xhFL0yPUO9nBU7NpqWEwXMQCtoZXshYs2uXdfZwWsHjeq8rkHqtv8isl1D
XiAVO2Lw9FI23NL3K4urw4oBaISAuzN61C2Y+50lkOnX6UtePKNxlpYnnMVkDVml
Rl7q6c+G3ybVJIYLJXtPoKYASSqyA1B467P6/1qtjNYD6PLbJFfBn+4akFeSN9U=
=5i/v
-----END PGP SIGNATURE-----
Other related posts:
