New Update Available
I fixed a bug that SergeyK discovered; "winsock add dword" was not exported in the dll (stringtable).
(note: you could use "winsock add int" as well, or for short ints you can use "winsock add word". what matters is the amount of bytes, not whether it is signer or unsigned. The exception to this is the float, where you have to use "winsock add float")
@SergeyK
here is a quick summary what to do on the receival side (copied from one of my posts on the first page):
Packet receival
1. recv message (allows channel to store the data)
2. split data into packets
3. while packet count()>0 do...
4. fetch packet (removes first packet from list and you will now operate on this packet)
5. get the bytes in the packet.
6. return to step 3 if packet count()>0
The most important things when using the inbuilt packet commands are:
1. packets have a limit of 255 bytes
2. you need to specify the type of the packet such that at the receiver side, you know what to do with it (what data to read out).
(note that point 1. is not valid if you use memblocks for sending data, there the limit is (8*1024bytes) = 8000+bytes
calculated in mind this is... about... 8192 bytes
BUT I can change this limitation if you want me. I can make it up to 64kb. but this is not needed actually ( I think )...