accesing socket at a lower level?
Z 3 Penguin
z3penguin at penguinpowered.com
Thu May 18 20:58:03 CEST 2000
Cedric Adjih wrote in message <8g0ool$q09$3 at ites.inria.fr>...
>Z 3 Penguin <z3penguin at penguinpowered.com> wrote:
>> I am working on writing python code to access the AIM servers. i have
>> looking at what my code sends out, and using something like
>> from socket import +ACo-
> Assuming the missing "s.connect(hostname, port)"
>(or "s.connect((hostname, port))"), your code looks correct.
>> tacks on some extra bytes at the beggining. this confuses the AIM
>> Any ideas? (Note: I am not good with C and am against having to write
>> in C)
>Hmm... What told you there were some extra bytes at the beginning?
>Are you sure:
>- AIM servers use TCP?
>- Python client is the problem?
Yes, because other AIM clients work fine.
>- Python socket C code is properly working?
Yeah, tryed it under both 1.5.2 (latest debian package) and 1.6a2 (tarball)
> (maybe try test_socket.py in somewhere in the library of Python
> -- /usr/lib/python1.5/test/test_socket.py or whatever -- or try
> one of the socker examples).
from socket import *
socket.error: (93, 'Protocol not supported')
More information about the Python-list