Am Donnerstag 08 April 2010 13:22:09 schrieb Todd Lewis:
> I happen to be facing exactly that same problem at the moment, so I'm
> hopeful (doubtful, but hopeful) someone will step up and prove me wrong.
Well, I won't. But why don't you both simply install a real Db server, like
PostgreSQL, for
On 04/08/2010 04:06 PM, Brandon Simmons wrote:
> For instance I envision a handful of clients on different machines
> each writing to a single sqlite DB every few seconds; would this
> defeat AFS's caching scheme?
>
> Thanks for the thoughtful responses.
Every few seconds your cached data is go
On Thu, Apr 08, 2010 at 04:06:18PM -0400, Brandon Simmons wrote:
>
> Thanks for the response. It seems like whole-file locking in sqlite
> would be a good choice for me in any case, and I can't imagine needing
> that kind of writing concurrency.
>
> Doing a little more research, this message desc
On Thu, Apr 8, 2010 at 2:18 PM, Matt W. Benjamin wrote:
> Hi,
>
> Simon is correct. A byte-range locking implementation for OpenAFS is being
> funded by Your File System, Inc., under its DOE SBIR Phase II grant. As
> stated elsewhere by Jeff, there are (or will be) structures for making
> com
Hi,
Simon is correct. A byte-range locking implementation for OpenAFS is being
funded by Your File System, Inc., under its DOE SBIR Phase II grant. As stated
elsewhere by Jeff, there are (or will be) structures for making completed
available to the community during the course of the work.
Ho
On 8 Apr 2010, at 12:22, Todd Lewis wrote:
In a word, no. If your multiple clients were on the same host, then
that
host could enforce the locking sqlite attempts, but from multiple
hosts
you lose.
This is actually only true on Linux. On other operating systems,
OpenAFS doesn't enforce
On 04/07/2010 10:10 PM, Brandon Simmons sent:
> I have a web application in which I would like many client web-servers
> to be able to read and write to many separate and modestly-sized
> sqlite databases, exported by a master server. Each database
> corresponds to an account, so we might have se
I have a web application in which I would like many client web-servers
to be able to read and write to many separate and modestly-sized
sqlite databases, exported by a master server. Each database
corresponds to an account, so we might have several concurrent users
accessing an individual DB every
