Closed sashee closed 11 years ago
Thank you for the fixes. the in-process client isn't default because I haven't had time to do so, and haven't looked at it as it isn't my code.
I'll need to review the codebase at some point and make some architectural decisions. Any feedback is greatly appreciated.
Cheers.
Could you please deploy a new snapshot version to the sonatype maven repo?
Will do. On 2013-02-14 7:06 PM, "sashee" notifications@github.com wrote:
Could you please deploy a new snapshot version to the sonatype maven repo?
— Reply to this email directly or view it on GitHubhttps://github.com/mboudreau/Alternator/pull/52#issuecomment-13537013.
Regarding the in-process client: I added that option primarily to allow easier breakpoint debugging of the Alternator code base by having the unit tests and the Alternator logic run in a single process. The spawned Jetty server version more accurately reflects the inter-process mode in which the real DyanmoDB is accessed by an application.
I mostly use it for unit tests in my application, and the in-process seems less overhead and as of now it seems stable
I have an app using DynamoDb, and I'm setting up a test environment. Alternator looks promising, but I've encountered some bugs, and also some missing features. With these changes, my app's tests are all ok with the inProcessClient (btw, why the server mode is the default? The in process one seems more useful). Also fixed a test that did not run with the inProcessClient.