Subj : Re: network programming in c
To   : comp.programming
From : dajava
Date : Mon Oct 10 2005 09:21 pm


moi wrote:
> dajava wrote:
> > Michael Wojcik wrote:
> >
>
>
> >
> >>Personally, for TCP/IP and sockets programming
> >
> >
> > I am not sure if this novice's question is suitable for this thread.
> > I was reading Jonathan Bartlett' message when I got the question about
> > telnet and tcp/ip.
> >
> > Say, there is a chess playing server. Choose any one. Which protocol
> > does it use?
> > I thought that kind of server used telnet. But a professional programer
> > told me his own server useed tcp/ip. Therefore, a chess playing can use
> > telent or tcp/ip. It relly up to its developers. Is that true? What is
> > the advantages and disavantages between telnet and tcp/ip for a chess
> > server.
> >
>
> The chess and go -servers that I know (Fics and derivatives, for short)
> have a listening port open (5000, IIRC for Fics). After accept() they
> communicate with their client with CRLF-delimited ASCII-strings.
>
> That allows people to connect to the server, using /usr/bin/telnet as
> their client program.
> The server recognises but ignores most (all but one ...) of the telnet
> options. (which is allowed by the RFC, IIRC)
>
> That is why the clients are sometimes called 'telnet clients', which is
> confusing. To say the least.
>

Do you mean that I am not the only person who is confused? :)

> Another source of confusion is the wording "chess playing server". The
> server does not play chess. It are the connected clients that play
> chess, exchanging moves (etc) with the server. Which just serves them.
> 
> HTH,
> AvK

dajava,

.