joyent / libuv

[jakescott]

Not sure how relevant this is:

"This is the new networking layer for Node. Its purpose is to abstract IOCP on windows and libev on Unix systems. We intend to eventually contain all platform differences in this library."

https://github.com/joyent/libuv


Some light reading for anyone interested :)

http://tinyclouds.org/iocp-links.html

[Benjamin van der Veen]

Yes, Kayak will run on libuv/oio with minimal tweaking.

[jakescott]

Video of Ry hacking on libuv :)

http://vimeo.com/24713213

[Benjamin van der Veen]

On Thu, Jun 16, 2011 at 5:56 AM, jakescott <jake...@gmail.com> wrote:
> Video of Ry hacking on libuv :)
>
> http://vimeo.com/24713213
>

This is giving me chills.

[Benjamin van der Veen]

Yeah, can't wait to get Kayak running on uv.

[panesofglass]

Have you started working on a simple .NET wrapper for libuv? If not, I'd love to work on it with you.

[Benjamin van der Veen]

On Aug 1, 2011, at 9:18, panesofglass <ryan....@panesofglass.org> wrote:

> Have you started working on a simple .NET wrapper for libuv? If not, I'd love to work on it with you.

Not yet. Kerry Snyder has something brewing and we were discussing some of the challenges of making cross-platform bindings for .NET last week.

I definitely think we should all collaborate on this rather than duplicate work.

Can't remember if he's on this list; but you should check out his project. https://github.com/kersny/libuv-csharp

My only beef with it is the C wrapper library. We had a long conversation on twitter about it which you might be able to dig up—the gist is that the uv struct widths vary based on platform so you can't reliably know how much memory to allocate on a given platform without a C compiler referencing it.

I thought about it this weekend and I think we should just use magic numbers. :S There would be 4 in total: *nix/win, 32/64bit.

b

[kerry....@gmail.com]

Yeah I'd gladly take any patches or contributions.. it's at the point right now where I can build and run a simple socket demo on Linux/OS X with Mono/Gcc and Windows with Visual C#/Visual C++, which in itself is pretty cool. This week I'm looking to finish up some little refactorings and take care of the rest of the (current) API (Pipes, Spawn) so hopefully next week I'll get a chance to look at moving most/all of it into managed land.