>I'm a little confused with the terminology. By field do you mean something inside of the HTTP Header instead of part of the address? And when you said a static page, did you mean that the skin/container/layout is static and the content is queried from a database?

Field was in reference to a table. All pages are entirely designed from the tables.

>It is better to have some kind of unique address for each separate 'record'. This can be a URL + querystring or it can be part of the URL. I mean that "http://www.levelextreme.com/wconnect/wc.dll" is the URL, "http://www.levelextreme.com/wconnect/wc.dll?5,2,5244" is the URL and the querystring, and "http://msnbc.com/123774/" is a URL with the querystring embedded into it. As long as each of these resolves to a single web page with relatively static content within the page then you are okay.

The encryption mechamisn takes, mathematically, longer to execute in real time. For all those tables that provides records to the Web, I will add a field in the table for the URL, which will already be encrypted. At run time, I will simply pull out this value instead of generating it. By that, an improve of performance, maybe not seen visually but mathematically, will be applicable as well as having fixed URL for Google and other robots which will not hammer the site as much as it is now.