Thanks!
That would be probably the best solution -- especially since all the “special”
activities I at the moment can think of are triggered by the state of the
objects in DB, i.e., I would not even need the requests.
Actually I have suggested this approach at the very beginning, but alas, the
What I have done is to have another app that processes this type of activity
and the main app just writes a "request" into a table that the processing app
polls. So any number of users can submit requests for processing and have them
accepted, but they are only processed sequentially, with an e
Hello there,
there are some activities of my application which should do only one instance
(e.g., archivation of objects). At the moment, I intend to
(a) add to my DB a specific table, say, T_LOCK; its rows would contain (at
least) ACTIVITY_ID (PK or at least UNIQUE), USER_NAME, and TIME_STAMP;
