Abdul,

I find the best way to think about using RJS is to break up your web page into distinct sections. Let's assume, for the purpose of this answer, that you have a Wibble which has_many Chunklets. Your Wibbles#show page has one section that displays a list of associated Chunklets, and that's what you want to update via RJS.

You'll want to display the chunklets section as part of the full show page (the HTML request), as well as send it as your RJS update. So, pull your chunklet list view code into a partial; let's say chunklets/_list.html.erb. Now, your widgets/show.html.erb view will simply render that partial:

page.replace_html('.chunklets', :partial => 'chunklets/list', :locals => { :chunklets => @chunklets }


This RJS will replace everything inside the div with class 'chunklets' with the contents of your partial.   As long as your pagination links are inside this div they'll be replaced each time you change pages, so they'll always be up to date.  Since you're rendering the same partial for both the HTML response and the RJS response you know your page will remain consistent.

Does that help?