4 ms·

You wouldn't use this on that case. This will be used when the data is already sent to the client side.

• dpcx 13y ago
  In what case would the data be "already sent to the client side" that doesn't involve essentially transferring the entire data-set? The search is certainly useful with 100 records, but if I can return only the 10 matching records from an AJAX request, that's 90 records I didn't have to return in the first place.
  • alttab 13y ago
    Great point. You could could progressively backfill the search to protect the initial load and user experience. You could cut down on overall bandwidth by only backfilling search data if the user has shown a preference for using search. The first search experience is a little slower, but overall system work and client side implementation using the posted method could provide a good balance.
  • Theriac25 13y ago
    One example I can think of is searching for matching documents with some other method (on the server side), and then searching inside each document with this method.
  • chii 13y ago
    but what if you had an infinite scroll ala twitter feed? then you can do client side search on that list without going back to the server.
    • dpcx 13y ago
      At which point, you've already transferred the entire data-set. I'm not saying it's not useful. I'm saying that it requires a lot of data to be "better" than server-side search.