Echo server: Difference between revisions

=={{header|C}}==

{{works with|POSIX}}

This is a rather standard code (details apart); the reference guide for such a code is the [http://beej.us/guide/bgnet Beej's Guide to Network programming]. The dependency from POSIX is mainly in the use of the <tt>read</tt> and <tt>write</tt> functions, (using the socket as a file descriptor sometimes make things simpler).

 

 

=={{header|C sharp|C#}}==

using System.Threading;

 

}

}

 

=={{header|Clojure}}==

<lang lisp>(use '[clojure.contrib.server-socket :only (create-server)])

(use '[clojure.contrib.duck-streams :only (read-lines write-lines)])

 

=={{header|Common Lisp}}==

{{improve|Common Lisp|There should be a http://common-lisp.net/project/usocket/ example.}}

Sockets is not a standard part of Common Lisp but many implementations have support for this. The following example {{works with|CLISP}}

<lang lisp>(defvar *clients* '()

 

=={{header|D}}==

This is a very basic server that processes the buffers one character at a time. In a real-world application, the buffers would be larger. More seriously, it processes one listener at a time. If the <code>currSock.receive()</code> blocks, the loop will not process other clients. This opens the door for a trivial denial-of-service attack. A realistic echo service must multiplex clients.

import std.socket;

import std.array;

 

=={{header|Erlang}}==

-export([start/0]).

 

{tcp_closed, Conn} ->

io:format("Connection closed: ~p~n", [Conn])

 

=={{header|F Sharp|F#}}==

let main _ =

EchoService

 

=={{header|Factor}}==

go echo(s, i)

}

 

=={{header|Haskell}}==

 

=={{header|Java}}==

<lang java>import java.io.BufferedReader;

import java.io.IOException;

{{omit from|PARI/GP}}

{{omit from|Retro|No concurrency support}}

{{omit from|Unlambda|Does not have network access.}}