Hello jun,
je> actually thats what im doing.. i have a separate table je> to save the loginid, session id<httpsession>, employee je> id, and the datetime it was accessed. everytime a user je> wants to edit an employee record, a row of info is je> inserted in this table.. when the user is done and je> save the modified record, the row is deleted.. for je> some reason if the user left the computer and the je> session expires or the pc crushes, we just cant leave je> the employee record locked, a daemon that would clean je> up the rows in the table that exceeded the maximum je> time.. lets say 1 hr... but what if the user is still je> doing something with the employee record, lets say je> computing the tax or for some valid reason. and the je> user exceeded the maximum time, the row in the table je> will be deleted by the daemon process.. the employee je> record is not locked this time.. and other users will je> be able to edit the employee record while the other je> user is still currently editing.. and there would be je> data collision.. je> please help me on this.. thanks... Maybe if someone tryes to apply any changes to the database after his time has expired he just gets a message that it is not possible? -- Best regards, Anton Tagunov mailto:[EMAIL PROTECTED] ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
