This problem does not happen on non-conversational pages. I'm hoping there's a
better solution than trying to set the requestDelay high enough to avoid issues.
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?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045560#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...