Erm... Someone appears to have subscribed a ticketing system w/ autoresponer to the Twisted mailing list; any chance a list admin could unsubscribe it? The email below claimed a "From:" of the m/l but a "Reply-To:" of support@mpcustomer.com On 05/09/2010 10:49 AM, twisted-python@twistedmatrix.com wrote:

Hello,

This is an automated response to inform you that your question has been entered into our system, and will be reviewed shortly. Your ticket has been submitted into the "General Support" department.

We will respond to you as soon as possible. > ============== Please keep this information, and use it when refering to your ticket:

Ticket subject: Re: [Twisted-Python] SQLAlchemy and Twisted Ticket number: 24487862 Ticket link: https://secure.mpcustomer.com/ticket.php?ticket=24487862 Ticket body: On 05/09/2010 07:07 AM, Daniel Griffin wrote:

...

If you let SQLAlchemy block twisted would there be any impact besides performance?

Depends how long it blocks for, and what else your process is doing.

With the reactor blocked:

* no socket reads or accepts can be done * no callLater or LoopingCall can be scheduled

...and so on.

If you've only got a small number of clients and no time-based scheduling and you're only blocking for a short time (tens or hundreds of milliseconds, say) it may be tolerable.

If the server has a lot of clients, or needs to accept new ones in a timely fashion, or has time-based work to do, and your blocking might go on for a while, it's probably not tolerable.

I'd avoid it personally (but then I'm utterly unconvinced by ORMs) and stick to using SA in a thread as your SQL query layer.

_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python ==============