 <p>Let us consider the pros and cons of doing this Server side </p> <p>PROs:</p> <ul> <li>You can do other processing on the data using the power of the server </li> <li>You are not subject to cross domain limitations like you would be in ajax </li> <li>Generally you do not have to worry about your server being able to access the resource, whereas on client you are at the mercy of users net restrictions, firewalls etc </li> <li>More control over your http response\request lifecycle</li> </ul> <p>CONS:</p> <ul> <li>You will have to consume more bandwidth sending the resulting data down to the client.</li> <li>You may have to do more work to leverage good caching practices</li> <li>Dependant on having certain server side libraries\framework elements</li> </ul> <p>Now although we have a much bigger list of Pros than cons... in the majority of cases you will still want to do this on the client... because the issue of double handling the data is actually a very big one, and will cost you both time and money.</p> <p>The only reason you should actually do it server side is if you need to do extensive processing on the data, or you cannot circumvent CORS (cross domain) restrictions.</p> <p>If you are just doing something simple like displaying the information on a webpage, then client side is preferable.</p>