Loggin what user does + concurrent access- best practices
Loggin what user does + concurrent access- best practices
- Subject: Loggin what user does + concurrent access- best practices
- From: Gustavo Pizano <email@hidden>
- Date: Tue, 7 Jul 2009 14:46:21 +0200
Well, Im gonna leave aside a little bit the problems Im having with the UI and focus more in the backend.
For this aplication I need to "key and eye" on what the user does, I have in my DB a table users with a relationship to translations table. like this.
USERS < >>TRANSFROMBASE.
So each user will have its own Session, and each time the User makes a translation I will add relationships and so on.
But there is more than one Translator, of course I can just tell the translators what they should translate, but of course they can translate even more that what I tell them to, in this case 2 translators can at the same time try to translate one word.
In this senario, what will be the best to do?
I hadn't read much about locking stuff, but I have seen that I can lock an object of a edditing context, whihc I have in mind wil lbe the defaulteditingcontext, I dunno if this will generate me a problem.
Then later I can with the admin tool that Im implemnting also, can check per/translator what thye have done and sign the paycheck.
few questions, should each translator have its own app instance, or thye must share the same?. It wasn't clear when reading the deployiment guide last week.... :S, i know i suck.
when a translator has selected a word to translate then I should lock that object immediatly until he/she save the changes, isn't?
what other properties or config should I have in order to make this thing happen?
Thanks
G.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden