Anonymous user
Talk:Chat server: Difference between revisions
→How to test it
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
Line 7:
: With the Tcl solution, a slow write is not (much) of a problem; the output is automatically queued until such time as the client can accept it (at a cost of some memory, of course; that's the source of the “much”, and it's possible to monitor it if necessary though that's rare). I don't know whether the Python solution is the same; it's the sort of thing that really benefits from deep event loop integration in the IO handling layer. (For the record, the Tcl solution should be “usable”. It lacks some features, e.g. authentication, but they're unlikely to alter the core of the chat app much.) –[[User:Dkf|Donal Fellows]] 09:49, 17 January 2011 (UTC)
:: That's all right. Authentication is not required for this task (keep it simple :). --[[User:Abu|Abu]] 10:06, 17 January 2011 (UTC)
==How to test it==
I've never used telnet before, thought the <code>telnet</code> command ''is'' installed on my Linux box.<br>
Can someone give me a run-down of how one might use that client-side command to connect and chat with some of these server implementations, so that I could use as a testing aid while developing my own server implementation for this task?
--[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 11:11, 6 August 2016 (UTC)
: simply enter <code>telnet localhost xxxx</code>, where "xxxx" is the port used by the server. Some of the examples use fixed port numbers, others require you to add it via parameter. C example uses port 7070, so <code>telnet localhost 7070</code> should do the trick.
:: It works, thanks! --[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 13:42, 6 August 2016 (UTC)
| |||