Method Permits
- Namespace
- MailFathom.Application.Access
- Assembly
- MailFathom.Application.dll
Permits(MailFathomPermission)
Answers the same question RequirePermission(MailFathomPermission) asks, for a boundary that has to decide rather than refuse.
public bool Permits(MailFathomPermission permission)
Parameters
permissionMailFathomPermissionThe capability being asked about.
Returns
Remarks
A transport that composes an answer per caller — a protocol listing offering only what the caller may call — needs the verdict rather than the failure, and asking it here is what keeps one definition of what holding a permission means. Every case RequirePermission(MailFathomPermission) refuses is answered false here, including work reached under no principal and work reached under a principal that is not a caller.
An unspecified permission answers false rather than raising, because the caller of this method is composing an answer about something it did not choose: a boundary asking about a capability nobody declared has found an operation nobody bounded, and the safe answer to that is no.