Question

I have been developing a project and in this project i have designed my code to do the same job after a specified time interval continuously. The job that wanted to be done has a lot of distinct cycles. The interval is small to execute them normally thus i used threads. Until that point everything is clear for me.

To decrease the process and information transaction i wanted to put an session like object that holds the given data and provide it to any thread at anytime. With this object i plan to not query the same configuration information from database at everytime but if it exists on the session take it else query and store on session.

I’m not sure how to implement this structure.

Regards,

Answer 1

That depends. There are several ways to keep and pass information in Java.

1. Applicationwide: declare it static and/or load it in a static {}.
2. Threadlocal: make use of ThreadLocal<T>.
3. Objects: put data in wrapper objects (javabeans?) which you just create once and pass around as c’tor/method arguments.

In your case I think either 1 or 3 is applicable. A real “session” is usually threadlocal, but your functional requirement (“provide to any thread at anytime”, “configuration information”) makes me think you’re rather looking for an applicationwide constant.