Opened 18 years ago

Closed 16 years ago

#664 enhancement closed wontfix (wontfix)

use reactor pool instead of internal pool

Reported by: Dave Peticolas Owned by: Dave Peticolas
Priority: highest Milestone:
Component: core Keywords:
Cc: Dave Peticolas Branch:
Author:

Description


Change History (4)

comment:1 Changed 16 years ago by Jean-Paul Calderone

Component: core
Priority: normalhighest

use reactor pool for what? pool of what? whatever it is, why is the reactor's pool better than an internal one?

comment:2 Changed 16 years ago by Dave Peticolas

This was a while ago, one of the core developers, I think itamar, suggested that adbapi's connection pool should use the reactor's thread pool instead of an internal thread pool. I think the argument was that using the reactor pool would mean you don't have to worry about starting & stopping the adbapi connection pool itself.

Personally, I don't have a problem with using an internal one, and I think an internal pool has it's own advantages, like controlling how many threads can be used specifically for database connections.

I'm happy to cancel this bug if it's no longer an issue for anyone. Not that I have time to actually implement it if it still is.

comment:3 Changed 16 years ago by jknight

I don't really see why this is desirable. If you don't either, it should probably just be closed wontfix.

comment:4 Changed 16 years ago by Dave Peticolas

Resolution: wontfix
Status: assignedclosed
Note: See TracTickets for help on using tickets.