drewB wrote: > I have been thinking lately about what should be executed client-side > vs. server-side and was curious what others thoughts are. > > Let's take the following example. A user has selected X pieces of > furniture. On a single page, they are > shown a list of the furniture items with specific info about each > piece (name, dimensions, manufacturer, list of parts etc). Much of > this info wouldn't be shown by default but is expandable. The user > can delete furniture items or add new ones. When they add a new one it > is immediately added to the page without reloading. >
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). In other words, for your furniture site, if you have 20 different types of furniture, and the user is likely to look at all or most of them, then client side. However, if you have ten thousand types of furniture, and the user is only likely to select twenty or so to look at, then server side - otherwise they will be downloading huge swathes of information that they won't actually need. -- Mike Cugley [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
