Pyro and sqlite3 problem

[Sébastien Ramage]

>         Off hand -- ensure that each remote access runs the entire sequence
> of "connect, cursor, execute, fetch, cursor-close, connection-close"
> rather than trying to, say, create a cursor in one access and then use
> that cursor on a second access...
>
>         Or maybe create one long-running thread to handle the database
> access and use queue objects to transfer the remote access parameters to
> the database thread, then retrieve from a return queue.
> --

thanks you for answer.
Do you think the first solution will be slow? I think I must use
locking to avoid problem.

The second solution seems better and looks like what I wanted to build
at first time, but maybe an ever opened sqlite database isn't a good
thing ?