What would be the best way of handling a relatively large list of thumbnails being passed to the browser (20 - 50) at one time?

Loading the whole set via services node really seems to slow things down, aka:
 
http://services.nirvanix.com/app/folder/thumb1.jpg
http://services.nirvanix.com/app/folder/thumb2.jpg....up to
http://services.nirvanix.com/app/folder/thumb50.jpg

How bad would it be to have the whole set pulling from node1 and thus skipping the redirect? If I recall, it would auto-redirect if it happened to have moved to another node, correct?

I realize this is contrary to the whole point of how you folks are balancing and spreading the load, but the additional response/redirect times seems to be outweighing whatever increase in download speed there might be on such small files.

Thanks!

You can call GetDownloadNodes with an array of paths to get the files node.  This would let you get all of the paths at once before rendering the page allowing you to replace the URL with the node path results.

If you decide to just call node1.nirvanix.com statically then you lose the benefit of having disaster recovery and natural balancing.  In the case the node does go down we will attempt to redirect you to another node but this is not for sure since we only are sure that services.nirvanix.com will exist and not  a specific node.

Regards,
     Barry R.

Good idea, I didn't think to use GetDownloadNodes. It would be much better to have one extra call from the server than to have 50 extra redirects on the client.

I don't in the documentation how many filePaths GetDownloadNodes accept at one time. What's the upper limit?

Thanks,

Adam
 

The number isn't set to a specific limit but you could be adversely affected if you pass too many.   The suggestion would be for around 100 to see good performance.  This is something you should test to see what works for you.

Regards,
    Barry R.