Thanks for your reply. What I want is the following.
1. A component I need is implemented to be thread-safe and handle
sessions. This means that the component itself does not manage
threads but it saves session data locally with reference to the
current thread.
2. I call this component which is a JNI-library (C++ & JNI files)
from my Java code, e.g. a web application. I want to be sure that
when I call the JNI library from the web application, the session
data stored in the library is always associated with the same user
thread. For example, the results from a second call should be based
on saved data from the first call.
The people developing the component tells me this is the way
sessions should be handled and that the Thread calling the library
is linked to the session data. They are C++ developers however and
I'm not convinced that this will work with Java in the same way as
with C++.
I also need to know if a web server like Tomcat already handles
sessions so that the same thread is always used for HTTP requests
with the same session ID (from cookie or URL). Or is it necessary
to handle threads yourself within the web application?
Many thanks, Josef
You should identify state by the session not the thread. A new
request in the same session will be handled by a new thread in tomcat.
Regards,
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden