-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/28/2011 12:41 PM, Drake Wilson wrote: > Back on the original topic, I would rather think a custom VFS sounds > like the way to go;
It is technically correct that will work. However it is a *lot* of maintenance work. The custom VFS would be a duplicate of the platform one (lots of code) but with only a very small number of lines changed. Imagine you want your own VFS where the only difference is that open() in the unixOpen implementation (235 lines plus others) is changed to myopen(). If you provide your own libsqlite then this is doable at compile time. If you want to use the version supplied by the distro vendor (normal Linux practise) then you are out of luck. About the only solution that will work for everyone is the ability to pass the VFS a table of function pointers that by default point to the operating system implementations (eg open(), access(), getcwd()). You can then override those as needed. This would require the VFS api be updated. Alternatively Chromium can be changed so that it traces the child and intercepts these calls returning data as appropriate. If there wasn't the need to deal with additional filenames then (on Linux) the filename could be passed as /proc/self/fd/NN. The default unix vfs could be changed such that filename pattern is recognized and NN+1 is treated as the journal etc. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1sDaoACgkQmOOfHg372QRDFACdEHjdrW8cEVB1lfKybxi+eL/g +1YAn1W5TpEl+ASRVkqji7DFknWLcnGM =DzRU -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
