Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: web counter, next-page method?

From: SunandaDH::aol::com at: 8-Apr-2004 3:30

> Maybe the only solution is that designer marks html section where such > "next-page" section will be placed, and it will be separated in another > few templates I will have to plug-in?
That's the approach we use at -- seems to work okay. Perhaps using RSP -- REBOL Server pages -- would help automate this sort of thing: For paged displays at, we add two parameters to the URL, start-atand limit=, for example: That gives power users the opportunity to edit the URL by hand -- example, to see all users on one page: 9999 Hallvard:
> Persistent connections / sessions would be better, but I didn't bother > using cookies or figuring out a good way to make session IDs and > putting them in the url. Guess this is easier with FastCGI.
Session ids are likely to upset search engines (they'll see a different URL each time they retrieve the same page, and may index none of them). But cookies upset users who don't or can't use them. With session ids, and Google, the two basic rules are: 1. don't use ID=xxxxxxxx as a CGI parameter name. It explicitly looks for IDand backs off, assuming it is a session id. 2. don't use anything that looks like a session id, so: S=1234 doesn't look like a session id (it's not ID= and the parameter is not a long string of apparently random characters) Best to have strings that are short. Especially, don't use integers above 9999. We do something like that at, so: and: both get you the same message, but the first probably looks like a session- id while the second probably doesn't. None of this matters if you don't want ot need the pages to be indexed by search engines. Sunanda.