The getter could be changed but this could break something elsewhere
I don't know where else this might be impotant. Instead I thought that
V6 is an oportunity to get rid of the old ballast
Yes, indeed. This change would require to check everything again in details.
I can affect any
Its TCP for sure... but the problem is that there are not terminators
(terminating strings/chars)...
Look at this... full dump from IRIS:
http://komputery.info.pl/PACKETS/fulldump_lan_ok.txt - packets are being sent
in one... whole BF2CC PL command answer was sent at once... - no problem here.
Waldemar Lukaszewski wrote:
Its TCP for sure... but the problem is that there are not terminators
(terminating strings/chars)...
The dump looks like a header is prepended that probably contain data
length. You need to know the header structure/size and the protocol as
well otherwise it will
Nice... and what does it mean ? :) I mean... how do i implement it?
Dnia 24-06-2006 o godz. 17:51 Dan napisał(a):
http://bf2.fun-o-matic.org/index.php/RCon_Protocol
Commands
All commands sent by the client have /n (0x0A) appended to indicate the
end-of-line. An optional 0x02 character can
Oh ... so this means that 0x04 is not being sent by the server and that
information is crap or there is something wrong with WSocket? Did you see
packet dump? There is on 0x04 at the end of command...
Dnia 24-06-2006 o godz. 19:46 Waldemar Łukaszewski napisał(a):
Nice... and what does it mean
doesnt have anything to do with how WSocket will split it...
It is not TWSocket which split packets, it is winsock. And it is perfectly
normal. TCP is a stream oriented protocl. That means datagram boundaries are
not preserved. There NOTHING you can do against that as long as you use TCP.
You
