Well, you have to avoid over the wire activity as it will cause a traffic pattern called a ³galloping herd². Basically servlet latency causing latency, causing.... And so forth. Your keyboard buffer will end up getting ahead of the over the wire call and end up with enough spooled key events to make it seem like your app has died.
The startup load is ³OK² but you have to deal with the impact of having the client-side data getting stale compared to the server. Perhaps limit the download to some number of characters allowing for the round-trip to occur after the user has typed in enough characters. Remember, although the numbers you present seem low, you have to plan for a much larger sample, one where the numbers of users substantially escalate or you wish to repurpose the algorithm in a more data-centric operation. K On 6/3/09 8:05 AM, "tchredeemed" <[email protected]> wrote: > > > > > > Basically, Our users have a group of Individuals (com.gladhandle.IndividualVO) > and in one part of the application they can search the individuals. > > However, one of our milestones is that they are able to search and the results > are refreshed on keyup of a textinput. > > Seeing as this could and would cause problems with the application if I hit > the back end with an AMF call every key up, I was considering loading all of > their individuals at startup. > > The majority of our users will have relatively small number of individuals (50 > to 100 or so). Some will have a lot (500 to 1000) and VERY FEW will have more > than that. > > Which path would be better, searching and filtering by making an AMF call > which would make a subsequent database call and roundtrip the information back > to me, or take the initial hit to load them all at startup? > > Thanks! > > > > >> > > Kevin F. Benz > [email protected] 425-785-7100 > http://www.kbenz.com > > "We can't solve problems by using the same kind of thinking we used when we > created them" - Albert Einstein >
