>Based on the numbers you provided, I have a hunch; are you referring the >message size *after* you've decoded it? If so, you need to take into >account that if the message is (for example) Base64-encoded, it has some >overhead due to the encoded values (as encoding packs multiple 8-byte >values into even more 7-byte values). The overhead is approximately the >size you're referring to. Other encodings have different sorts of >overhead, but all in all, encoded messages are usually somewhat larger >than their decoded counterparts. > >Once again, I might be totally off the tangent here, and if the scenario >I've painted is not valid in this case, I sincerely apologise for having >jumped to conclusions :) Yeah wrong example :). Even through on receive message after decoding is smaller by 33% if it was base64 encoded.
I said that this happens on only busy networks. When a lot of packets are flying on the wire. Where total download size is a lot larger than total size reported by server. Regards, Miha -- It's time to get rid of your current e-mail client ... ... and start using si.Mail. It's small & free. ( http://simail.sourceforge.net/ ) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
