We are porting a client server application on J2EE technology. The old app was holding locks on different object in memory, so each client could very get an answer from the server if a certain object was locked or not, very fast.
Of course, this memory area was unique to the server, and protected to accesses from different threads.
We now want to simulate this behavior with the new J2EE app. Is is possible to have a UNIQUE memory area in which to store the lock info, or do I have to store this information into the database.
Any help would be greatly appreciately.
-
J2EE and memory data (1 messages)
- Posted by: Gabriel Nicula
- Posted on: April 07 2005 10:15 EDT
Threaded Messages (1)
- J2EE and memory data by Charles Lee on April 08 2005 03:29 EDT
-
J2EE and memory data[ Go to top ]
- Posted by: Charles Lee
- Posted on: April 08 2005 03:29 EDT
- in response to Gabriel Nicula
Of course is an option to have the lock data in the database but hvae you thought of using JMS as a queing mechanism? This will possibling solve you problem without any lock