This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Developer Beta

 
Ramesh kumaar
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear All,
Incase of developer beta i guess there is no need of DataInfo, FieldInfo class as we had in Developer. Please give ur openions.
The Spec says for lock as follows.
// lock a record so that the record is only accessible to this
// client.
// throws RecordNotFoundException if record recNo does not exist
// or is marked deleted
// throws RecordLockedException if the found record is already
// locked
public void lock(int recNo)
If this is the case what is the need for locking I mean if some can modify a record even its been locked someone else. Please share ur views.
regards,
rameshkumar
 
Ramesh kumaar
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can any one explain what to be done exactly.
The Spec says:
"Locking must be implemented as advisory locking. That is, attempts to modify a locked record
will succeed, regardless of where the lock was given. However, attempts to lock an already-locked
record, or to release the lock on a record that is not locked, must fail".
-rameshkumar
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think this means that you do not need to add a call to lock or a check to make sure a lick is there when the modify method is called.
If your client uses the lock(), read(), modify(), unlock() order then it is really a non-issue that modify() does not have any checks.
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic