-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seaduk: Implement Libuv Bindings in C #5
Comments
What should I tackle next? DNS will be useful for network clients as the TCP module doesn't resolve domain names. FS isn't for loading app resources since the zip bundle APIs handle that, but it would be useful for other fs stuff. Process would allow spawning child processes and creating multi-node "clusters" where a server can share load across CPU cores. |
This work is paused while I work on the rusty duck version. |
+1 for DNS |
Depends on #2
This can probably reuse much of my dukluv project, but I suspect the design won't match exactly and will need heavy tweaking.
uv_loop_t
uv_handle_t
uv_timer_t
uv_prepare_t
uv_check_t
uv_idle_t
uv_async_t
uv_poll_t
uv_signal_t
uv_process_t
uv_stream_t
uv_tcp_t
uv_pipe_t
uv_tty_t
uv_udp_t
uv_fs_event_t
uv_fs_poll_t
The text was updated successfully, but these errors were encountered: