hi there, i thought it best to bring this to someone's attention. the forkingmixin code keeps track of its children, plus because it forks, there's no close_requests() to interfere with the operation of the child etc. etc. now, for some marginally bizarre reason, adding an extra base class - BaseServer - has, i believe (without proof, just a hunch), caused a bug in ThreadingMixIn to be more likely to occur. now, i wrote BaseServer in order to be able to overload this for a server that reads from a SQL server table and performs actions based on what it reads from there (the name of a host and the name of a python script to action on the host, from the database :) :) ... but i don't do threading. python is my first actual exposure to thread programming. does anyone have enough experience with threads to write something in less lines and less time than this message? all best, luke ----- Forwarded message from noreply@sourceforge.net ----- Delivered-To: lkcl@angua.rince.de Delivered-To: lkcl@samba.org To: noreply@sourceforge.net From: noreply@sourceforge.net Subject: [ python-Bugs-417845 ] Python 2.1: SocketServer.ThreadingMixIn Date: Thu, 03 May 2001 16:26:12 -0700 Bugs item #417845, was updated on 2001-04-21 08:28 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=417845&group_id=5470 Category: Python Library Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Guido van Rossum (gvanrossum) Summary: Python 2.1: SocketServer.ThreadingMixIn Initial Comment: SocketServer.ThreadingMixIn does not work properly since it tries to close the socket of a request two times.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4