True, but you probably know the protocol just as well as I do, so I kinda assumed that any specific details would have already been pointed out.
Anyhow, aside from any hardcoded client/server limitations (and obvious memory/hdd limitations on either end), it seems the maximum file size, according to the protocol, is 2^32 bytes.
* Large File Transfer
* <p/>
* <pre>Packet Layout
* Field Length Description
* 0 2 Core Packet IDs: 0x00, 0x0A
* 2 4 Total File Size
* 6 ... File Chunk
* </pre> |
Though, considering each packet is roughly 512 bytes, large file transfers probably should be avoided anyway.
Bak - Sun Jan 21, 2007 1:05 pm
Post subject:
I disagree with your reasoning but agree with your conclusion. Using bigger packets wouldn't speed up file transfers, in fact if they cause packet fragmentation it would probably slow down the transfer. Also, a 4 gigabyte file limit (2^32 bytes) is hardly a concern.
Anyways the limit is 4,194,304 bytes, and it appears to be client side. Any files larger than this will not download (the progress stays at 0%). Currently ASSS doesn't check for this, so clients will just be stuck at 0%. I didn't actually wait for the smaller files to download... but they did tick around to 1% unlike the larger file.
3,997,510 bytes - got to 1%
4,193,790 bytes - got to 1%
4,250,734 bytes - stuck at 0%