Re: Non blocking socket server and storage engine

2008-11-19 Thread kdeveloper
On Nov 19, 10:51 am, Lawrence D'Oliveiro <[EMAIL PROTECTED] central.gen.new_zealand> wrote: > kdeveloper wrote: > > The server needs to run at least three threads: > > Get it working without threading first. Lawrence, I was following article [1] when building my code. So I guess it should be ok. A

Re: Non blocking socket server and storage engine

2008-11-19 Thread kdeveloper
On Nov 19, 10:57 am, "Chris Rebert" <[EMAIL PROTECTED]> wrote: > Quoting from Wikipedia (http://en.wikipedia.org/wiki/User_Datagram_Protocol): > "UDP does not guarantee reliability or ordering in the way that TCP > does. Datagrams may arrive out of order, ***appear duplicated***, or > go missing w

Re: Non blocking socket server and storage engine

2008-11-19 Thread Chris Rebert
On Wed, Nov 19, 2008 at 2:36 AM, kdeveloper <[EMAIL PROTECTED]> wrote: > Hello Pythonists, > > I am building a non blocking socket server for incomming UDP packets. > The server needs to run at least three threads: > 1. getting data and pushing to "some" storage (at the moment I use > queue), > 2.

Re: Non blocking socket server and storage engine

2008-11-19 Thread Lawrence D'Oliveiro
kdeveloper wrote: > The server needs to run at least three threads: Get it working without threading first. -- http://mail.python.org/mailman/listinfo/python-list

Non blocking socket server and storage engine

2008-11-19 Thread kdeveloper
Hello Pythonists, I am building a non blocking socket server for incomming UDP packets. The server needs to run at least three threads: 1. getting data and pushing to "some" storage (at the moment I use queue), 2. acknowledge the package received 3. retrieve the information from the storage and in