On Saturday, June 7, 2003, at 09:39 AM, Wojciech Kocjan wrote:
If noone has tried to write sqlite driver for nsdb, then where can I read more on how to write one myself? sqlite api seems pretty straightforward.
This is a good candidate for an external driver, which would guarantee that no more than a single thread (and process, for that matter) is using the SQLite API at a time, while still making concurrent connections available through AOLserver. Look at the Sybase driver for guidance.
Actually, this is quite interesting, but I have no idea on where to read on it.
I've read some more on SQLite and it seems that it has a locking mechanism which prevents different threads/processes from doing a concurrent read-write access. So, locking is not what I should matter.
It is interesting, however, that I should be able to create an isolated process, running at a different UID/GID, and being able to do things like daily backup - ie commiting and then calling tar or something (this could be done by sending some special request from AOLserver :).
With the current implementation of the external driver protocol, don't run the external proxy in remote mode -- only use it on the local machine so it connects by pipes, because the latency of an actual TCP connection is too high for the protocol being used.
I'm downloading nssybpd and nsibasepd, I guess pd means proxy driver. It seems pretty straightforward.
I'll try and do a hello world driver, which simply returns some result based on the text.
Any other material I should look into?
-- WK
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
