anonymous wrote : The problem with that approach is that the proper value for requestDelay depends on the responsiveness of the server (which depends on load, hardware, etc). | | Would there be a way for seam to handle this more gracefully?
This is an interesting question, if it's only a conversation causing issues... The only other alternative to blocking requests while one is currently processing in a conversation (which is more or less the point of having a conversation in the first place) would be to be able to configure the conversation to abandon a currently processing request if a new one comes in. I think that might be opening a big can of worms -- first from a security perspective, and it may even change notions and definitions of what conversations are and how they should behave. Or did you have something else in mind? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045572#4045572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045572 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
