Funny behaviour of MySQLdb

[Heiko Wundram]

Hey Alex! Hey List!

Thanks for the advice on threads, and I'm going to try to implement that
some time now. The main problem is that the server needs to handle
multiple requests at a time, as several servers create a network in
which they do an "Identify" at some times. This identify works to create
a routing table of the whole network, which is distributed to every
server... Of course this method doesn't need database access, but still
it would be nice to have a working way to have multiple threads
accessing the database.

On the other hand, the people writing MySQLdb explicitly stated the
approach I chose now. and I guess someone should tell them that this
approach is far from bug-free... ;) I guess I'll post something to their
ML this night.

btw. If anybody is interested in the project as a whole, once I get it
to work, then just say so. What this server basically does is offer
XML-RPC services to a frontend, and is especially well suited to get all
that database and user administration code out of a web-application.

It allows for recursive and distributed queries, in which case all
servers (or a certain server which is found in the routing table) is
queried for the function.

The backend server imports modules on startup, which just stick to a
certain interface, but that's it. Programming a module for the backend
server is very simple.

As I said, if anyone is interested, feel free to mail me; I guess I'm
going to put the whole thing under the LGPL anyway.

Yours,

	Heiko W.