thank you for advice.
changing the requestDelay helps really. Thanx for that tipp.
Now I can type in my filter-condition without getting my text overwritten. But after the set requestDelay is over, the filtering is done character by character. So the table is quite often rerendered and that takes in total a long time.
Try increasing request delay.
thanx for your answer.
I tried values up to
but that doesn't change the problem.
I understand this attribute
requestDelay - Attribute defines the time (in ms) the request will be waiting in the queue before it is ready to be sent.
that the requests are queued and after that time in ms all requests are sent. What I want is not n Requests for n characters of my filter-criteria. I want 1 request for my whole filter-criteria.
While requests are waiting in queue, they are combined into a single request if came from the same component. If I set requestDelay=300 for queue, then, while I'm typing, requests are not sent. After I stopped typing and request delay passes, single request is sent. If I start typing again, they will be combined into a single one and sent after request delay triggered by me stopped typing.
Is this scenario satisfiable for your requirements? Looking at "10000" delay it is 10 seconds delay - very huge. So I want to confirm: does this work as I've described or not?
10000ms was a test, at the moment I use 800ms.
You are right up to a certain point. If I type in 3 characters as filter criteria the table isn't rendered the moment I'm typing. But after I stopped typing and a certain time (depending on value of requestDelay) the table is rendered (I didn't check whether there is a request sent to the server, but I can see the table filtering/rendering) character by character. In my case 3 times. Also if I delete the filter criteria.
For me this:
"After I stopped typing and request delay passes, single request is sent."
is not working. My structure at the moment is:
<a4j:support event="onselectionchange" reRender=".../>