Actually, more significantly for me is that the default localhost SocketPermission is checked before a more lenient SocketPermission. In theory, one should be able to introspect SocketPermission instances and determine that one may be automatically implied by the other so can be skipped, possibly saving a lookup. Chris
Peter Firmstone wrote: > A big problem with the current implementation is SocketPermission blocks > other permission checks from proceeding.
