Sometimes it is impractical to cache an entire page because portions of the page may need to change on each request.In those cases, you can cache just a portion of a page. After routing has determined which controller to use for a request, your controller is responsible for making sense of the request and producing the appropriate output.

ids[]=1&ids[]=2&ids[]=3” as “[” and “]” are not allowed in URLs.

Most of the time you don’t have to worry about this because the browser will take care of it for you, and Rails will decode it back when it receives it, but if you ever find yourself having to send those requests to the server manually you have to keep this in mind.

All interactive programs provide two basic functions: obtaining user input and displaying the results.

Web applications implement this behavior using two HTTP methods: POST and GET respectively.

This is a rare case when I recommend reading as little about it as possible before trying it out, because it confused the heck out of me at first; and the truth is, you will rarely interact with AJAX in its “raw” state — you will usually use helpers such as j Query.

If you are creating a page on your website where users can modify their profile, you could use AJAX to update a user’s profile without needing to constantly reload the page whenever they submit the form.This simple protocol gets broken when application returns web page in response to POST request.Peculiarities of POST method combined with idiosyncrasies of different browsers often lead to unpleasant user experience and may produce incorrect state of server application.Caching is inevitable for a high-performance, scalable web application.There are different types of caching that have already been implemented in hybris.This is pretty much the same problem as the JAVA one posted earlier.