clipper@no15sun.csd.uwo.ca (Khun Yee Fung) (09/26/90)
If you know the talk protocol, can you send a copy to me? Thanks. Khun Yee -- ---- In Real life: Khun Yee Fung clipper@csd.uwo.ca (Internet) Alternative: 4054_3267@UWOVAX.BITNET UUCP: ...!{ihnp4|decvax|seismo}!{watmath|utzoo}!ria!csd!clipper Department of Computer Science Middlesex College The University of Western Ontario London, Ontario, N6A 5B7 CANADA
epeterso@encore.com (Eric Peterson) (09/27/90)
clipper@no15sun.csd.uwo.ca (Khun Yee Fung) writes: | If you know the talk protocol, can you send a copy to me? Thanks. You can get the source for talk yourself and take a look at it. It's available via anonymous FTP from ucbarpa.berkeley.edu (I'm not sure what subdirectory it's in). This is the best way to figure out just how Talk actually works. The code is pretty well-written and easy to follow. Talk uses a very simple protocol. After the connection is made between the two clients, the first three characters sent by each client to the other client are the delete character, delete word, and delete line characters in that order (I think that order is right -- check the source to make sure). After the first three characters, ALL other characters sent are intended for display on the remote system. Good luck with it! Eric -- Eric Peterson <> epeterson@encore.com <> uunet!gould!epeterson Encore Computer Corp. * Ft. Lauderdale, Florida * (305) 587-2900 x5208 Why did Constantinople get the works? Gung'f abobql'f ohfvarff ohg gur Ghexf