> To me, the balance between Server-side and Client-side comes down to how > much of the information you have available on your site is actually > going to be used in any one session. > > If most of the data is going to be used, then you're as well downloading > it once (Client-side). > > If most of the data is *not* going to be used, only download that which > you actually need (Server-side).
Agreed, this is very important. Don't send data that probably isn't going to be used. You can always make AJAX calls to retrieve data that you don't have already, making it look like it was already there. That also makes it alot easier to handle non-javascript browsers using the same controller and views. So, list your furniture names and, for example, make them expandable. If expanded, a piece of data is retrieved from the server. This is a fast request. If javascript is not enabled, you can easily reload the page with the piece of furniture you want expanded. Otherwise you would, for example, be sending hidden information about every piece of furniture along with every non-AJAX request, which is definitely -not- going to be used. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
