>If I use Cookieless=True it of course mangles the urls which means there
is no browser caching of the pages, so it is slow.
The browser WILL still cache the pages. The session ID remains the same
all the time as long as you don't force it to create a new session by
linking to a page without including a session ID.
The fact that the URL becomes:
/(bktylw45s3f14345r3w4lx2j)/catalogue.aspx
...is no different to if it was:
/catalogue/catalogue.aspx
It's just a folder name and doesn't affect client side caching at all.
If I were you, I'd use cookieless=true.
Just ensure that your links in the website start with "~" rather than
"/" or otherwise you'll create a new session. ~ gets resolved to the
correct URL for the current session if you pass it through
Server.ResolveUrl(). You don't need to call ResolveUrl manually for most
internal functions that take URLs as arguments.
eg Response.Redirect("~/basket.aspx");
You might also have to convert some hard coded links (HTML) to
asp:HyperLinks so you can use the "~" and thus avoid creating new sessions.
Note that ~ doesn't work in <a> tags. It's a server side macro only.
Hope this helps.
Nick...