-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/01/12 18:48, Ryan Macy wrote: > Would there be any reason SQLite would have a hard time functioning in > a database as a service model?
SQLite lives in the same process as the code using it. > Each user would generate a database (or many databases) and connect to > it with an API. The SQLite API is for use in the same process. If you have to connect to a service then it requires a completely different API. The introduction of latency and the completely different API, the need to identify and authenticate, authorization etc would make this a very pointless exercise. There are plenty of existing database servers that meet those needs, already have remote APIs and ways of overcoming latency etc etc. Have you even used SQLite? Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk8gyUYACgkQmOOfHg372QRdaACfbKRwYVMYyybPDxHiiu5oQpMc GlgAoLgFa1tgG2fdrIatIw2XT1clmr9V =pxXp -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
