Hi all,
We are pleased to announce the release of Slim3 RC1.
Slim3 is a full-stack MVC framework optimized for Google App Engine/Java.
Our main concept is Simple and Less Is More. Less is more means
simplicity and clarity lead to good design.
The main features of Slim3 are as follows:
* Global
Hi Yasuo,
Wow, this look neat! I'll go ahead and add this to open source projects.
One question, though: do you have any unit testing examples? E.g. how
would I mock out the datastore or write a Controller test?
On Tue, Mar 9, 2010 at 12:42 AM, Yasuo Higa higaya...@gmail.com wrote:
Hi all,
cute framework
NM
On Tue, Mar 9, 2010 at 4:17 PM, Ikai L (Google) ika...@google.com wrote:
Hi Yasuo,
Wow, this look neat! I'll go ahead and add this to open source projects.
One question, though: do you have any unit testing examples? E.g. how
would I mock out the datastore or write a
There is some interesting stuff in the release, but I've browsed the
Global Transaction stuff and I'm a little scared.
(http://sites.google.com/site/slim3appengine/slim3-datastore/transactions/global-transaction)
It seems that in the code it writes out a task in a queue to close the
commits,
Hi Ikai,
One question, though: do you have any unit testing examples? E.g. how
would I mock out the datastore or write a Controller test?
Slim3 supports Test-Driven Development.
You can find more information here:
Hi Scott,
It seems that in the code it writes out a task in a queue to close the
commits, possibly. I'm pretty sure transactions should not be
implemented using queues, for any reason. The complexity of storing
temporary lock/tx objects in the datastore, time spent during that
transaction,
On Tue, Mar 9, 2010 at 7:07 PM, Yasuo Higa higaya...@gmail.com wrote:
Slim3 locks an entity group when getting, putting and deleting entities
so that nobody updates the entity group. So it never happens
that the first two entity group transactions commit and the third fails.
What do you do
Hi Jeff,
Slim3 locks an entity group when getting, putting and deleting entities
so that nobody updates the entity group. So it never happens
that the first two entity group transactions commit and the third fails.
What do you do when there is a lock conflict?
ThreadA locks Resource1
