You should not try to implement that directly in the CMS page, if you are implementing a reports feature of some kind you should implement supporting pages that can use your parameters. For example the SiteModuleControl part (this is the part of the feature that lives on a cms page) of your reports feature could be just a list of reports, you can do ajax paging in it so that it does not change the url or need to use the url. Then from the list you link to your supporting page(s) and pass in the moduleid and pageid as well as your specific params like reportid.

Notice that is exactly how the forums work, the part that is on a CMS page is just a list of forums on the page http://www.mojoportal.com/forums.aspx and from there it links to supporting pages.

Things that plug directly into the CMS pages need to be able to behave well even when other things are also on the same page, so query string params and postbacks can be problematic. You can do postbacks in a SiteModuleControl but to avoid troubles for other features on a page it should redirect out of postback after completing the postback logic or else use an ajax postback al la UpdatePanel or other ajax techniques.

So from your list you might link to an actual physical supporting page like ReportDetail.aspx and pass in all the needed params.

You supporting pages should inherit from mojoBasePage so you can have the same skinning applied and can take advantage of methods in the base page for validating security. If you look at the code for existing features you will get the idea.

Hope it helps,

Joe