Live data from Hacker News

iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search

labs.stephenou.com

1–10 of 38 posts

Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search

#5

Lots of people jumping on the Google Instant train... Anyways, towards your iTunes instant: Why not offer the possibility to preview songs from your web app? You get the preview URL via the API!

Good idea. I think that is totally possible through HTML5 right?

Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search

#6

Lots of people jumping on the Google Instant train... Anyways, towards your iTunes instant: Why not offer the possibility to preview songs from your web app? You get the preview URL via the API!

Good idea. I think that is totally possible through HTML5 right?

Yes. Check out Marco Arment's preview.fm. He had a similar web app that allows you to preview album.

Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search

#8
post #6

Earlier quoted context omitted.

Good idea. I think that is totally possible through HTML5 right?

Yes. Check out Marco Arment's preview.fm. He had a similar web app that allows you to preview album.

Oh yeah, I've heard about it before. I will definitely implement it using if it doesn't heavily affect loadtime.

Re: iTunes Instant, Solve 2 Huge iTunes Problems: Cluster Interface & Slow Search

#9
post #7

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 :)

Yeah, 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.
Post reply on HN