I can only tell from my experience.
2003 i had just learned about blitz3d
2004 messing with TCPIp whooo why to it lagg.. fault trace and so on...
2004 Found the bugg.
My server Halts cause the TCPIP buffer Lying in tcpip.
Packets seam to arrive difirent times. and this cause TCPIP readavail lying about size of buffer.
2005 Found the workarond for that Nasty tpcip lag. Its simple medecine is to have Static size of packet, and have a sneaky sending.. i
So in order to create a good running engine in blitz3d tcp. there is soem basic rulze.
1) Always have static size of tcp packet size.
2) Always user readavail() before readbytes()
3) Always user readbytes(),Sendbytes()
Never ever putt more than 8k into the stream :D
I dont say its easy to understand. I just says it works good if propper used.
Also there is no GOOD tcpip engine at CodeAcrive.. thats saad :(
2003 i had just learned about blitz3d
2004 messing with TCPIp whooo why to it lagg.. fault trace and so on...
2004 Found the bugg.
My server Halts cause the TCPIP buffer Lying in tcpip.
Packets seam to arrive difirent times. and this cause TCPIP readavail lying about size of buffer.
2005 Found the workarond for that Nasty tpcip lag. Its simple medecine is to have Static size of packet, and have a sneaky sending.. i
So in order to create a good running engine in blitz3d tcp. there is soem basic rulze.
1) Always have static size of tcp packet size.
2) Always user readavail() before readbytes()
3) Always user readbytes(),Sendbytes()
Never ever putt more than 8k into the stream :D
I dont say its easy to understand. I just says it works good if propper used.
Also there is no GOOD tcpip engine at CodeAcrive.. thats saad :(