It’s important in for other ways as well. In general search engines will only index a limited number of parameterized URLs (typically well less than 100). As all APEX URLs have params, most pages on a large site won’t get indexed. One way around this is to create a site index that dynamically generates all the URLs, and register that index with Google. Unfortunately, Google’s rules don’t allow ANY redirects in a site index. Hence the need for session zero and the need that it not do a redirect.

One more not on this fix. It had an unfortunate side effect that on that very first page, when using session zero, you can not programatically add to the http header. I’m sure very very few people will try to do this, but I logged it as a bug and I think it will be fixed in the next release.

Anton

If I find something interesting on asktom then I will paste the url, which includes the session_id, into my blog and google will consider the page to be unique. Now that we can use a session-zero those in the know can replace the session_id with a zero and the page will no longer be unique. But removing the session_id will do the same thing, so this has never been an issue for those in the know.

For this feature to make an ApEx app more visible on the web, each page would have to have those little buttons which allow you to link from digg, facebook, reddit, etc etc…the number of little buttons on some sites grows by the month! And people would have to use the buttons rater than simply copy and paste the URL. I doubt this feature will push ApEx apps to the top of google’s listings.

The session id does not belong in the url. That’s the real issue.

Great news, I have been waiting for this one. We will upgrade our enviornments and hopefully everything will work perfect with session 0 now.

Olivier