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

Investigation: File Descriptors in the style of Netburner's approach #88

Open
phillipjohnston opened this issue May 4, 2019 · 0 comments

Comments

@phillipjohnston
Copy link
Member

Could we do something like this for the framework?

  • Netburner SDK
  • The NetBurner environment integrates the RTOS, TCP/IP stack, and other peripherals with a file I/O system based on file descriptors. A file descriptor can be described as a handle to a network socket, serial port, system peripheral, or any other object that can be read or written to. Most of the API functions pass a file descriptor as a parameter to such an object
  • By default there are a maximum of 255 file descriptors:
  • • 0 – 2 for stdin, stdout and stderr
  • • 3 – 4 for the first two UART serial ports, 0 and 1.
  • • 5 – 128 for TCP (32 in total)
  • • 129 – 250 for expansion (additional UARTs, TCP sockets, or custom)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant