node 0.5 / libuv port (was: eio_custom execute callback should return void.) about protobuf-for-node HOT 5 OPEN

Yes, I expect to build against the eio version exposed by node. Same for v8 
(added this to the doc).
node 0.4 ships with a version that expects an int.

Are you trying to replace the eio in node?

I am not, I guess the build system for node 0.5 has changed somewhat
because protobuf_for_node could not find the header eio.h at build
time and I only later noticed it was included in node's private
headers.

I guess for node.5 the idea would be to use their new "libuv" layer to make it 
work on Windows, too:

 int uv_queue_work(uv_loop_t* loop, uv_work_t* req, uv_work_cb work_cb,
    uv_after_work_cb after_work_cb);

http://markmail.org/message/3ogv22w56slz2esl#query:+page:1+mid:3ogv22w56slz2esl+
state:results

Ah I see, thanks for clearing that up.  Is this something being worked
on already for protobuf_for_node?

I took a quick look. While the apis are almost one-to-one, the uv_async_* 
family has a slightly different interface & semantics (nothing is really 
documented...) - so I currently seem to get the reference count of the event 
loop wrong and termination-on-idle doesn't work yet. I'll try and fix that 
tonight. If not, I can still check it into a new branch for you.

Let's turn this into the node 0.5 issue.