I agree that one needs to be careful. I do understand the performance problems that could arise if you are making lots of round trips to the server.
In this case I bind to: autosuggest="#ValueList(desc.description)#". So since I already have the results of the query I don't think there would be any roundtrips. The biggest thing is once I type a letter and some results are returned, then eliminating them as you type should require almost nothing, just drop off those that no longer match. With CFAUTOSUGGEST you have to pause for anything at all to happen. So essentially you have to pause 1/2 second after every letter to let the list refresh and see your new options. This is not good and as I said my users will go bezerko. 1/2 second may not seem like alot but when you multiply that by every letter, and the fact that my users will be using this lookup every time they enter a new record which is every 30 seconds to 2 minutes, then you see how those little pauses may drive one crazy. On 8/6/07, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote: > David, > > >..5 isn't really fast enough. I know my users are going to scream. > >Maybe it's not the speed. But this is not working as I had hoped. > >Once you start typing I would expect all matches to show up and then > >the list would eliminate items which no longer match as you continued > >typing. With cfautosuggest you have to pause for the amount of time > >in AUTOSUGGESTBINDDELAY before the list will pop up. > > > >So, nothing really happens until you pause. The Javascript function I > >was using before worked as I expected. Your list popped up > >immediately and items were eliminated as they no longer matched > >without any delay at all. This Javascript function also used the > >results of a query. > > > >Am I stuck? Any way to tweak cfautosuggest? > > Are you binding to an AJAX call or a local array? > > If binding to local array, I agree the timeout you specify should allow a > smaller amount. > > However, when dealing w/AJAX calls you've got to be extremely careful that > you don't flood the server with AJAX calls. This would be easy to due if you > set the timeout too low. > > The problem with CFMX 8 adding lots of AJAX functionality is developers > don't have to have understand what's going on behind the scenes. I think > it's extremely important that Web Developers really understand AJAX and the > potential server issues you introduce implementing lots of AJAX on a site. > > That's not a knock on AJAX and I think it's great Adobe has made great > strides to make implementing complex DHTML easy to use--it's just I think > it's extremely important to really understand what's going on behind the > scenes. > > Where I'm going with this is that it wouldn't surprise me if Adobe purposely > was trying to limit users from setting an obscurely low delay speed--since > it could have serious impact on the server. > > However, that's only an issue if you're binding to an AJAX call. > > -Dan > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:285498 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
