[nanomsg] Re: Alpha Python bindings.
- From: Martin Sustrik <sustrik@xxxxxxxxxx>
- To: nanomsg@xxxxxxxxxxxxx
- Date: Wed, 28 Aug 2013 06:38:33 +0200
On 28/08/13 01:30, Paul Colomiets wrote:
I guess for high level API
you should make a class for each socket type, and a method/property
for each socket option anyway, so that user don't need to use
constants anyway.
What's the upside of such approach?
The downside, obviously, is that any change to the library (new
protocol, new socket option) would require a change to the binding.
Consequently, the binding won't be in sync with the lib all the time,
more maintenance work will be required etc.
Martin
Other related posts:
