OO design and multiple local sockets

Andy Dent dent at oofile.com.au
Tue Feb 4 03:03:04 EST 2003


In article <mailman.1043930275.5885.python-list at python.org>, Andrew
McGregor <andrew at indranet.co.nz> wrote:


>received on, and from where.  So far, so good.  It's threaded (pretty much=20
>necessarily).  There are two pools of sockets for two different protocols=20
>that have to interact.

>What I can't figure out is what a clean OO design for the socket handling=20
>looks like, managing the various queues and worker threads without getting=20
>really hairy.  Can anyone help?
Have a look at http://beepy.sourceforge.net/ which is a very clean,
threaded implementation of the BEEP protocol.

G'day from West Aussie

-- 
Andy Dent BSc  MACS  AACM    http://www.oofile.com.au/
OOFILE - Database, Reports, Graphs, GUI for c++ on Mac, Unix & Windows
PP2MFC - PowerPlant->MFC portability




More information about the Python-list mailing list