{"comment":{"created_at":"2011-10-20T07:41:09Z","body":"Yup it most certainly lacks polishing !\r\n\r\nI'm curious as to why you would use ruby arrays for the task ? This tracking feature should be an internal mechanism not to be available from ruby.Is that still possible using ruby arrays (I'm completely new at writing C extensions for ruby). ","updated_at":"2011-10-20T07:41:09Z","url":"https://api.github.com/repos/zeromq/rbzmq/issues/comments/2465680","id":2465680,"user":{"avatar_url":"https://secure.gravatar.com/avatar/3dd7898b4d7162daf154f789465f7c03?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3dd7898b4d7162daf154f789465f7c03","url":"https://api.github.com/users/zetaben","id":73409,"login":"zetaben"}},"action":"created","issue":{"number":16,"created_at":"2011-10-19T14:52:48Z","pull_request":{"diff_url":"https://github.com/zeromq/rbzmq/pull/16.diff","patch_url":"https://github.com/zeromq/rbzmq/pull/16.patch","html_url":"https://github.com/zeromq/rbzmq/pull/16"},"body":"Hello, \r\n\r\nThese commits create a list of open socket per context. When ruby is freeing things up, the unclosed threads should now be closed first before calling zmq_term. \r\n\r\nI asked for thoughts about this feature on the mailing list :\r\nhttp://lists.zeromq.org/pipermail/zeromq-dev/2011-October/013814.html\r\n\r\nThanks for the gems\r\n\r\nRegards","comments":2,"title":"Tracking open sockets","updated_at":"2011-10-20T07:41:09Z","url":"https://api.github.com/repos/zeromq/rbzmq/issues/16","id":1994672,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/3dd7898b4d7162daf154f789465f7c03?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"3dd7898b4d7162daf154f789465f7c03","url":"https://api.github.com/users/zetaben","id":73409,"login":"zetaben"},"html_url":"https://github.com/zeromq/rbzmq/issues/16","labels":[],"state":"open"},"legacy":{"issue_id":1994672,"comment_id":2465680}}