Cool..After some more testing, I found a good portion of the delay went away when I turned caching back on.  I had turned it off since I was actively tweaking things.  I guess Tapestry was rereading things on every ajax call as well.

Thanks!

Birch

On 11/30/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
That's the default delay value of the Autocompleter I'm using...I can probably make it parameterizable..Lemme double check.

Yep, it's just a little parameter. I'll add these parameters into it before we cut the alpha-7 release today.


On 11/30/05, J B < [EMAIL PROTECTED]> wrote:
There seems to be a very noticeable delay in the auto completer I am testing with.  It takes almost a second between the key press, and the method invocation to return the list, and about half a second to render the list.  The return part I am not so worried about, but I don't see why there is a big delay up front.  I am running locally, and should have no network bottlenecks slowing me down.

Any thoughts?

Thanks!

Birch


Reply via email to