...and of course typically there is a limit on how many items to be returned for auto-suggest, but taking it into considiration ruins all fun of arguments. :-)
"Jeremy Dunck" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] On 11/14/05, Maniac <[EMAIL PROTECTED]> wrote: > But I think this whole approach is wrong and should not be supported. > There are certain reasons behind separating server and client part and > wishing to break this barrier smells like a bad design to me. If Django > will make such things easy then I can easily imagine people doing > "select * from client where name like 'A%'" on a key press and > complaining that this Django thing is slow... I think some Ajax libraries may already get this right, but it seems to me this sort of thing should be there. What I mean is, instead of the naive keypress event handler, you'd want to chunk it so that any event would fire after n millisecs of inactivity, and any previously pending request of the same class would be cancelled (since it's wholly redundant of the latest request enqueued. But that has nothing to do with django. :)
