Sometimes, the S2 page won't give a damn about them, like the page=4 argument... the page just re-runs and its data structures already have page 4 populated in all the ranges.
But, sometimes the page will care.
Imagine a layout that's framed... the main page is the frameset. The framed documents are the same code, but run with a different arguments.
I could imagine framed IndexPages, but let's talk about a framed GalleryPage...
/brad/galler/2343434 -- frameset... big top area, small scrolling bottom area
/brad/galler/2343434?framearg=top -- "Click a picture below"
/brad/galler/2343434?framearg=bottom -- All the thumbnails
Then, clicking something in the bottom brings up a PicturePage in the large frame.
So, the question is... do we give S2 pages access to all the URL parameters, or only a restricted subset?
I'm in favor of a restricted subset... I foresee too many misuses if they had complete access.
So then, what's the subset? What do we call the arg? "framearg" is kinda lame.
And while we're at it, what are the names for the other args? I want URLs to be consistent (as much as possible) if people change styles. Obviously if the page size changes, or security of pictures change, or picture reordering happens, page=n arguments are no longer good.
Still, what do we call the page argument? "page"? "p"?