One thing we could look into is the twisted libraries. It looks from the source like apt-proxy uses twisted for most of its networking features. Twisted is still under active development:
One thing I don't know is if apt-proxy circa 2005 isn't fouling up somehow with twisted circa 2008. Ideally, APIs stay stable long term, but you never know.
From reading http://twistedmatrix.com/projects/core/documentation/howto/internet-overview.html it looks like it should be possible to write apt-proxy's networking code so that it doesn't choke on hung/broken client connections or multiple simultaneous requests. Still daunting, given I know nearly nothing about Python yet. Maybe we can work on this some during the summer, Rolf. :)
One thing we could look into is the twisted libraries. It looks from the source like apt-proxy uses twisted for most of its networking features. Twisted is still under active development:
http:// twistedmatrix. com/
One thing I don't know is if apt-proxy circa 2005 isn't fouling up somehow with twisted circa 2008. Ideally, APIs stay stable long term, but you never know.
From reading http:// twistedmatrix. com/projects/ core/documentat ion/howto/ internet- overview. html it looks like it should be possible to write apt-proxy's networking code so that it doesn't choke on hung/broken client connections or multiple simultaneous requests. Still daunting, given I know nearly nothing about Python yet. Maybe we can work on this some during the summer, Rolf. :)