-
1. Re: the serious design defect of richfaces
nbelaevski Aug 21, 2008 9:07 PM (in response to careprad)Hello,
We're now thinking about enhancing of queues in 3.3.0: https://jira.jboss.org/jira/browse/RF-3131.
Please vote for this feature if you like it here: http://wiki.jboss.org/wiki/RichFacesFuture -
2. Re: the serious design defect of richfaces
careprad Aug 21, 2008 10:17 PM (in response to careprad)thank for you reply,but I think I can't wait for the new version,I found such comment in the source file:
// Submit or put in queue request. It not full queues - framework perform waiting only one request to same queue, new events simple replace last.
// If request for same queue already performed, replace with current parameters.
A4J.AJAX.Submit = function( containerId, form, evt , options ) ,maybe what you say is enhanceing this queue,isn't it? -
3. Re: the serious design defect of richfaces
sergeysmirnov Aug 22, 2008 1:13 AM (in response to careprad)There is no quick fix solution for this problem. Otherwise, we did not live with it for all two and a half years.
Yes, the length of the queue is 2. Most people who use RF even have no idea that this is a problem somehow. I remember a couple time, probably, people met it. However, only you announce it as serious defect. -
4. Re: the serious design defect of richfaces
careprad Aug 22, 2008 5:32 AM (in response to careprad)Richfaces is good frmaework,it do most thing very well,that is why we choose it.
But to us,this is really a serious problem,if we can't resolve this problem,the whole ui project should be refactored--change to another ajax-jsf framework or change the server-side framework,but the second one is impossible,the web is just one of many UIs of our server-side framework.
I think I have found a solution now,to modify the submitRequest function of the a4j engine,put all the request to a client queue,and a timer poll this queue.Hope I it work!
thank for your reply.