@Roel
That's a nice
thread. I've read it and I'm still not convinced.
The only thing that could possibly convince me to use 2-tier is if it was a must requirement.
As you said it is not as you and many others passed with it.
My only concern was this lock cookie. If I put a locking into a server then the cookie would be completely unnecessary.
But choosing two-tier would introduce many problems. For example:
1.
findByCriteria and
readRecord
If I do this on client side I would need to verify the result on the client side (a record might be modified between calling of find and read). Why would client ever wanted to verify the output from the server?
That would mean checking the same condition twice (once on the server and once on the client) and I think it's not good idea.
I could create
findAndGet method on then server side...
But if I do this (add a method to provided interdace) why not just introducing
book and using it instead of
lock/
update/
unlock?
2. Client crash before unlock.
3. Client needs to know how to translate
String[] into
Room...
If you knew that
all solutions should implement a thick client why did you write a thin one?