comment on

Pardon me for not reading two hundred lines of socket code before lunch, but the way the question was phrased, I think I might know the problem.

Sockets provide streams of data. A message that took one call to send, may take three calls to read. Or vice versa. With TCP, you can't assume that all of your message will be available at the same time. You can only assume that it will all eventually arrive, in order, or the socket will close.

Therefore, if the boundaries of data elements are important, then you need to put markers in the data stream itself, in such a way that you know if you have the whole data element, or even the whole marker, before you start using the data. If you don't have the whole marker, wait and read again, and then see if you have the whole marker.

Again, sorry for not studying the whole code, but as someone else posted, there are some good modules that already do TCP packets for you. Another place to look is Chapter 12 of Advanced Perl Programming (by Srinivasan).

--
[ e d @ h a l l e y . c c ]

In reply to Re: Transmit file over socket by halley
in thread Transmit file over socket by AcidHawk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks