Hi Johan,
Thanks for the information. Unfortunately I can't use the threaded model. This isn't state between invocations but is system wide configuration data. Things like does the admin have to approve new user registrations. It changes extremely rarely, but I'd prefer not having to go back to the database to check on a regular basis so caching it in the service makes sense.
--Chris
On Apr 27, 2005, at 2:01 PM, Johan Lindquist wrote:
Hi Chris,
Should be no problem with synchronizing your calls ... But if you are looking to store state in between invocations (with result of the invocation being stored) of the service, you should probably look at the threaded service models (see http://jakarta.apache.org/hivemind/current/multithreading.html for details) for your implementation.
Cheers,
Johan
On Wed, 27 Apr 2005 13:24:37 -0700, Chris Conrad <[EMAIL PROTECTED]> wrote:
Hello,
For several of my services I'd like to keep some system preference information. Rather then hit the database to retrieve that data all the time, however, I'd like to keep it in a private field. I didn't see anything explicit about it in the documentation, but could there be any problems with having synchronized service methods?
--Chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- you too?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
