Socket Programming in Python

[Premshree Pillai]

For the uninitiated: "Socket Programming in Python" at
evolt.org: http://evolt.org/article/Socket_Prog...276/index.html

=====
-Premshree
[http://www.qiksearch.com/]

_______________ _______________ _______________ _______________ ____________
Yahoo! India Insurance Special: Be informed on the best policies, services, tools and more.
Go to: http://in.insurance.yahoo.com/licspecial/index.html

[Irmen de Jong]

Re: Socket Programming in Python

Premshree Pillai wrote:[color=blue]
> For the uninitiated: "Socket Programming in Python" at
> evolt.org: http://evolt.org/article/Socket_Prog...276/index.html[/color]

Hmm. I'd stick to http://www.amk.ca/python/howto/sockets/

But, ofcourse, only if you really need to use raw socket communication ;-)

--Irmen

[omission9]

Re: Socket Programming in Python

Premshree Pillai wrote:
[color=blue]
> For the uninitiated: "Socket Programming in Python" at
> evolt.org: http://evolt.org/article/Socket_Prog...276/index.html
>
> =====
> -Premshree
> [http://www.qiksearch.com/]
>
> _______________ _______________ _______________ _______________ ____________
> Yahoo! India Insurance Special: Be informed on the best policies, services, tools and more.
> Go to: http://in.insurance.yahoo.com/licspecial/index.html
>[/color]
What a retarded tutorial. If that article is any indication of Mumbai
University it seems that institution is to be about on par with an
american vocational high school.

[Josiah Carlson]

Re: Socket Programming in Python

> from socket import *

is not required. In fact, that leads to namespace pollution that may
cause problems for users later.

Most socket applications that I've seen tend to use 'import socket',
then refer to all the various constants by socket.AF_INET and such.

Another thing worth mentioning is that while UDP datagrams are useful
when you don't care about your data, TCP streams tend to do what people
expect (no information gets re-arranged, etc.).

- Josiah