[storm] Pylons and Storm

[Christopher Armstrong]

On 8/20/07, Vsevolod Balashov <vsevolod at balashov.name> wrote:
>
> Ok. My "Database" class may be bug or may be feature. I don`t know.
>
> I make commits and rollbacks in threads and cant find differences
> between 1 connection or many =)
>
> If this feature don`t like - just not use it :)



IMO, it really is a bug. It breaks all the assumptions that Storm makes
about the database backend. You probably haven't noticed any problems yet
because your concurrency has not been high enough, or you don't have enough
users exercising the code at once, or your data manipulation is very simple,
or just by accident — but you *will* run into problems your application
scales in any of these aspects. It is very similar to thread programming in
general; it's very easy to think you have code that works until the kernel
pre-empts you at a time you didn't expected to be pre-empted at, and it
often won't be noticed until you're already in production. The same applies
here.

I don't have the time to write up an example of the bug right at the moment,
but it should be pretty simple to fix if you just leave out your Database
class entirely. The thing I still don't understand is why you thought you
needed to add that implementation of Database at all.  Were you trying to
solve another problem?


-- 
Christopher Armstrong
International Man of Twistery
http://radix.twistedmatrix.com/
http://twistedmatrix.com/
http://canonical.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/storm/attachments/20070820/9f3608e1/attachment.htm