Henke! Have we met on IRC ? I operate there as butter. Used to hit up actionscript and papervison3d on freenode but it's been a while.
Ross P. Sclafani Owner / Creative Director Neuromantic Industries http://www.neuromantic.com http://ross.sclafani.net http://www.twitter.com/rosssclafani 347.204.5714 On Feb 16, 2012, at 5:20 PM, Henrik Andersson <[email protected]> wrote: > Mattheis, Erik (MIN-WSW) skriver: >> I'm not understanding something here - in the following excerpted and >> simplified example, I'm trying to send a ByteArray of length 170 and there >> seem to be 173 bytes received. Where are the "extra" bytes coming from and >> and is that the reason readObject returns null? (tracing >> _socketData.toString shows that the object properties I want to work with >> are in the ByteArray): >> > > As I said before: > >> This means that you MAY get more than one object in one go and that > you MAY get only a part of the object(s) at the ends of the buffer. > > It is highly possible that multiple writes was stuffed into one read, > even if you don't flush between the writes. > > The three "left over" bytes could be the first three bytes of the length > of the next object. > > Your code must be able to deal with the crazy situation that it got a > full length int, the encoded object and only three quarters of the > length int for the next object in one go. > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
