On 7 May 2008, at 18:03, Tom Leighton wrote:
> Have you checked its not sending 2 packets ? With the rest of the
> packet
> following?
No, but given that the protocol specifically defines how such a
situation would be handled by the first 4 bytes of the reply being
0xFFFFFFFE rather than the reply I'm seeing of 0xFFFFFFFF I doubt
that has much to do with it. The replies are also very small (~100
bytes) so I don't see why they'd be split across multiple UDP datagrams.
FWIW:
[EMAIL PROTECTED] ~/src $ python
Python 2.5.1 (r251:54863, Jan 17 2008, 19:35:17)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> udpsock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
>>> udpsock.connect(("213.228.232.26", 27015))
>>> udpsock.send("\xFF\xFF\xFF\xFFTSource Engine Query\x00")
25
>>> udpsock.settimeout(10)
>>> a = udpsock.recv(1400)
>>> b = udpsock.recv(1400)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
socket.timeout: timed out
Good idea though. :)
Ciao.
-Chris
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
