. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 JULIA_PKG_SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 29.2 External package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that

package called Sockets. Let's first create a simple server: julia> using Sockets julia> @async begin server = listen(2000) while true sock = accept(server) println("Hello World\n") end end Task (runnable) usage is some- what simpler than the raw Unix socket API. The first call to listen will create a server waiting for incoming connections on the specified port (2000) in this case. The same function may PipeServer(active) Note that the return type of the last invocation is different. This is because this server does not listen on TCP, but rather on a named pipe (Windows) or UNIX domain socket. Also note that