anonymous wrote : FYI, before this thread got going I'd been thinking (vaguely) in terms of using read/write locks in AS 6 to better handle coordination. E.g., in ClusteredSessionValve acquire a RL before passing the request down the pipeline, release when it returns, acquire a WL before handling replication. Basically, allow concurrent access to a session but lock out requests while a thread is replicating. |
In the current case, the application code is synchronizing on the session facade object, so they would be left out if we synchronize on an internal r/w lock. I wonder if we could somehow expose our (HTTP session level) r/w lock object to the application (in a reasonably portable way), so that they could also get a RL when getting the attribute values. Applications will also want to get a WL when setting attribute values. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240384#4240384 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240384 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
