Hi. Actually sso login mechanism is doing some file_exists calls that can be avoided:
1) no ssohandler is provided in kernel, so no need to search in kernel for it. we're told to add new stuff in extensions and leave the kernel as is...
2) after this check, ez loops over extension directories to find ssohandlers files. But authoload mechanism should already know in which file the class is, so, no need to check for the existence of the file again... right?