4 ms·
All of these jsonp / iframe based instantizers have to be putting load on servers (probably not in great volume, but still). There's a reason Google had to put
by mcs 16y ago
All of these jsonp / iframe based instantizers have to be putting load on servers (probably not in great volume, but still). There's a reason Google had to put special consideration into how to make the ajax-endpoints scale :)
- stephenou 16y agoYeah, I agree. I will probably cache search results if load time is too slow. Also, I have a 0.5 second delay (after keyup) to execute the search function.
- VincentJones 16y agoIn terms of scalability, YouTube Instant will encounter lots more problems than iTunes Instant. It's full-length video vs. 100x100 artwork image.
- mcs 16y agoFor Youtube Instant, the actual search terms are hitting suggestqueries.google.com for the autocompletion, which is what is powering google.com. The actual video coming through is likely from a CDN, which are already built upon an infrastructure for scaling. Probably not as big of a deal as you think. Bandwidth wise it's unlikely that somebody watches the entire video as much as they rapidly hit different videos.
- fatalerrorx2 16y agoI created a YouTube Instant Search and it's not hitting any road blocks... it loads all videos and image thumbnails from YouTube, and auto suggestions from Google and it loads pretty fast check it out: http://www.youtubeinstantsearch.com http://www.youtubeinstantsearch.com