History

Cory Benfield b05c6f2206 Move NIO to NIOPosix, make NIO a shell. (#1936 ) Motivation: The remaining NIO code really conceptually belongs in a module called NIOPosix, and NIOCore should really be called NIO. We can't really do that last step, but we can prepare by pushing the bulk of the remaining code into a module called NIOPosix. Modifications: - Move NIO to NIOPosix - Make NIO an umbrella module. Result: NIOPosix exists.	2021-08-16 16:50:40 +01:00
..
README.md	Add 2 missing server readme docs. (#940 )	2019-04-02 11:28:31 +01:00
main.swift	Move NIO to NIOPosix, make NIO a shell. (#1936 )	2021-08-16 16:50:40 +01:00

Move NIO to NIOPosix, make NIO a shell. (#1936 )

Motivation:

The remaining NIO code really conceptually belongs in a module called
NIOPosix, and NIOCore should really be called NIO. We can't really do
that last step, but we can prepare by pushing the bulk of the remaining
code into a module called NIOPosix.

Modifications:

- Move NIO to NIOPosix
- Make NIO an umbrella module.

Result:

NIOPosix exists.

2021-08-16 16:50:40 +01:00

README.md

Add 2 missing server readme docs. (#940 )

2019-04-02 11:28:31 +01:00

main.swift

Move NIO to NIOPosix, make NIO a shell. (#1936 )

2021-08-16 16:50:40 +01:00

README.md

NIOUDPEchoServer

This sample application provides a simple UDP echo server that sends clients back whatever data they send it. Invoke it using one of the following syntaxes:

swift run NIOUDPEchoServer  # Binds the server on ::1, port 9999.
swift run NIOUDPEchoServer 9899  # Binds the server on ::1, port 9899
swift run NIOUDPEchoServer /path/to/unix/socket  # Binds the server using the given UNIX socket
swift run NIOUDPEchoServer 192.168.0.5 9899  # Binds the server on 192.168.0.5:9899