Resource model / *.tdb file locking

[Harry]

Hi Jon,

while I appreciate the new work on a Resource model, keep in mind that
it is now an either/or choice on how to use cloudkit (via http or the
resource model).

Imagine cloudkit started as part of a rack stack and was configured to
use - say 'cloudkit.tdb'. This file is now locked and not usable by
any other process.

Or am I missing something entirely!?

Cheerio, Harry.

[Jon Crosby]

Using Tokyo Tyrant Tables should take care of this. However, I was just running some tests with this setup this afternoon and found that transactions are not supported in that environment. There is an assumption in CloudKit::Resource around transaction availability (which are available using TC Tables rather than TT Tables). To take care of this, a slightly different strategy is needed in the update and delete methods. I'll jump on this today. With that problem solved, using TT Tables will solve the file locking problem you mentioned.

-Jon

 

Cheerio, Harry.

[Jon Crosby]

The master branch on GitHub now has the transaction fix for Tokyo Tyrant Tables. This should take care of multiple ruby processes accessing the same data. There is a new example in the examples directory demonstrating its usage.

-Jon

-Jon

 

Cheerio, Harry.

[Harald Weppner]

Hi Jon,

fantastic - I'll give it a try and report back.

Cheerio, Harry.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CloudKit" group.
To post to this group, send email to clou...@googlegroups.com
To unsubscribe from this group, send email to cloudkit+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cloudkit?hl=en
-~----------~----~----~----~------~----~------~--~---