[zeromq-dev] Forcefully drop a peer connection

Mike Owens mikeowens at gmail.com
Sun Jul 17 20:50:12 CEST 2011

I've been looking through the code. I may if I get time.

On Sun, Jul 17, 2011 at 1:10 AM, Martin Sustrik <sustrik at 250bpm.com> wrote:
> On 07/15/2011 05:15 PM, Mike Owens wrote:
>> It would be helpful if there were api functions that allow three basic
>> low-level socket operations:
>> 1) A callback or hook of some kind that is called before accept(), which
>> includes basic peer info (remote ip) allowing the program the option of
>> refusing the incoming connection.
>> 2) The ability to check whether connect() actually connected to the
>> remote host (valid tcp/ip connection), avoiding the need to have to send
>> a ping and infer from a timeout.
>> 3) The ability to drop a connection. The remote side should be able to
>> detect this via some intterupt code (e.g. EDISCONNNECTED or something
>> like that).
> There's a plan to create a new low-level socket type in the future that
> would replace ROUTER and allow to circumvent the messaging patterns and use
> 0mq as a dumb networking framework. You can help with the work, if you are
> interested.
> Martin

Mike Owens
마이크 오웬스

More information about the zeromq-dev mailing list