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

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)