The benefits are the same as they would be for any application that wants to use SQLite instead of a traditional database: trivial install and configuration, simple administration, etc. Were SQLite to support higher concurrency then these benefits could be extended to a wider variety of applications. The point is try to identify the technical issues that have stood in the way thus far and distilling them to something simple that can be explored and hacked on without diving too deeply into SQLite internals.
Iker Igor Tandetnik wrote: > > A better question may be - what's the benefit? What's the point of the > exercise? What's the advantage over the traditional server architecture? > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Iker Arizmendi AT&T Labs - Research Speech and Image Processing Lab e: i...@research.att.com w: http://research.att.com p: 973-360-8516 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
