(05-27-2015, 12:18 PM)frocco Wrote: I am not understanding this. If you have an Auth Module, most likely every module in your app might require it.
Are you talking controller to controller calls or a view calling different controllers?
Authentication/authorization are often core functionality for any application which uses them. In that case, I would probably lean towards making a library (or libraries) which provides an interface (and probably a basic implementation) for this functionality. The library could be structured similar to the database library or session library, allowing "drivers" to define the underlying implementation, and some careful planning could allow those "drivers" to be loaded from modules, based on configuration. Supplying a basic implementation with the library also permits failover to that basic implementation when the module is not available (though proper configuration should make that an uncommon occurrence).
In the end, though, that level of effort is only really going to be appropriate for certain situations (or when you're building a base which you plan to reuse indefinitely on multiple projects). In a simplified system, your use of that particular feature can be easily tied to a base controller, which could act as the intermediary provided by the library in my more complicated example.
