[nanomsg] Re: The nanoconfig preview
- From: Paul Colomiets <paul@xxxxxxxxxxxxxx>
- To: "nanomsg@xxxxxxxxxxxxx" <nanomsg@xxxxxxxxxxxxx>
- Date: Fri, 4 Oct 2013 18:21:04 +0300
Hi Martin,
On Fri, Oct 4, 2013 at 6:12 PM, Martin Sustrik <sustrik@xxxxxxxxxx> wrote:
>> The `nc_close` replaces `nn_close` because the real processing is done
>> inside separate thread, so the socket must be closed inside that
>> thread too.
>
>
> What's exactly the work that's done in the background?
>
Requesting config and executing nn_connect/nn_bind/nn_setsockopt is
done in background. The need for nc_close to be in background is to
avoid race condition of nn_close with
nn_connect/nn_bind/nn_setsockopt.
>
>> I'd like project to be moved to nanomsg organization, to encourage
>> more people to experiment with it.
>
>
> I've added you nanomsg organisation admins, you should now be able to move
> the project.
>
Thanks. Just moved a repo to:
https://github.com/nanomsg/nanoconfig
--
Paul
Other related posts:
