A great way to do this. There are plenty of other ways. Just identify the data in any way you like so you can classify it on the receiver.<br><br><div class="gmail_quote">2010/1/17 Thorbjørn Lindeijer <span dir="ltr"><<a href="mailto:bjorn@lindeijer.nl">bjorn@lindeijer.nl</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sun, Jan 17, 2010 at 19:50, Alex Milstead <<a href="mailto:alex.milstead@gatech.edu">alex.milstead@gatech.edu</a>> wrote:<br>
> Also, Jay you mentioned earlier that it was easy to do simple data-type<br>
> checking on the receiving end. I'm a bit of a fledgling network programmer<br>
> -- I'm still definitely becoming more acquainted the vast amount of<br>
> unfamiliar programming techniques in this particular arena. The only<br>
> surefire type-checking system I know about in programming is in java (=/),<br>
> with it's "instanceof" operator. As far as I know this type of mechanism, or<br>
> anything similar, doesn't really exist in C/C++. So my next question is, if<br>
> we're sending binary data along and receiving it as binary data, what's the<br>
> most efficient way of type-checking the probable struct being piped through?<br>
<br>
</div>You give it a number which designates its type. You'd usually prepend<br>
such a number to each of your messages, so that you know how to<br>
interpret them on the other end.<br>
<br></blockquote></div><br>Cause united breaks guitars<br><a href="http://www.youtube.com/watch?v=5YGc4zOqozo">http://www.youtube.com/watch?v=5YGc4zOqozo</a><br><br>