I have been having fun working with sockets in Metacard, and in general everything
seems to work fine.
Some socket questions:
When using sockets to read and write I have been using the following approach: write
the length of the packet on a line followed by the data, at receiving end read for one
line, then read for the supplied number of characters. What approaches do others use?
You can also read without specifying a "for" condition, a specified handler will be
called when data arrives. Are there any advantages/disadvantages of one approach over
the other?
In general, if you have two stacks that are going to have an ongoing series of
communications going backwards and forwards, is it better to leave the socket open, or
always close the socket after each communication. I've assumed the latter.
Presumably there is a limit on the number of sockets MC can have open?
When MC has an open socket, does it periodically attempt to verify whether the remote
party is still present?
Any other comments or tips from people who are experienced using sockets in Metacard
would be appreciated.
Rodney
--
--
Rodney Tamblyn
Educational Media group
Higher Education Development Centre, 75 Union Place
University of Otago, PO Box 56, Dunedin, New Zealand
ph +64 3 479 7580 Fax +64 3 479 8362
http://hedc.otago.ac.nz ~ http://rodney.weblogs.com
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
