Skip to content
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

Socket calls or callbacks? #12

Open
palerikm opened this issue Mar 16, 2015 · 1 comment
Open

Socket calls or callbacks? #12

palerikm opened this issue Mar 16, 2015 · 1 comment

Comments

@palerikm
Copy link
Contributor

Should spudlib do a send()? Or rely on the application to provide a callback so it can send the packets on the applications behalf?

A discussion regarding portability and ease of implementing into existing stacks would be good. Maybe supporting both the above scenarios at compile time is a viable option?

@hildjj
Copy link
Contributor

hildjj commented Mar 21, 2015

tube_set_socket_functions() does most of what you want at relatively low overhead both at runtime as well as for the programmer. For evidence, see _mock_sendmsg and _mock_recvmsg in tube_test.c. I'm open to doing more; perhaps getting this running on Windows as well as a more... "custom" operating system would give us more specific requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants