Preventing WCM from generating sessions when content is accessed anonymously

Earlier today, I had a call from a friend who was trying to work out why he was seeing 000s of sessions created on his Portal/WCM delivery server when content was being accessed anonymously, via the WCM servlet, using the URL /wps/wcm/connect ( as opposed to /wps/wcm/myconnect ).

As I started to dig into the problem, he called me back and confirmed that he'd resolved it by creating a new Custom Property, public.session=false, for the WP_NavigatorService.

He's done a far better job of explaining it here: -

http://metkhoo.blogspot.com/2009/09/getting-rid-of-anonymous-sessions-when.html

Ironically, I was on my way to the same solution, albeit from a slightly different direction - I found this: -

http://www-10.lotus.com/ldd/portalwiki.nsf/dx/07052009031730WEBAKH.htm

which refers to the same Custom Property.