On Sun, Jul 22, 2007 at 04:49:45AM -0700, Trevor Talbot wrote: > Okay. Well, for most of the client/server databases, they already > have an event model to piggyback on: network I/O. Since sqlite is > embedded, it doesn't have one to use, so you have to roll your own. > Many people just dedicate a thread to sqlite work, and pass messages > back and forth to other threads using whatever method fits in with the > rest of their application.
Would it seem reasonable then to write an sqlite server ? A separate app with say an XML-RPC interface or similar ? (I don't like threads) :) With other RDBMS such as MySQL, Oracle, FireBird, Postgresql they more or less should support asyncronous queries right ? cheers James -- -- -"Problems are Solved by Method" - - James Mills <[EMAIL PROTECTED]> - HomePage: http://shortcircuit.net.au/~prologic/ - IRC: irc://shortcircuit.net.au#se Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
