Redux Authentication 1.4a (24th July 2008)

[eluser]kirilisa[/eluser]
I actually have a couple of questions regarding this library (good job by the way).

First & most important, why do you have it set up so that the library calls/passes through to the model and not the other way round? I'm actually not that used to the distinction between library and model (when I've designed my own simple frameworks I've just had controller, view and a model/API which serves as both model & library) but I was under the impression that a Library is necessarily more generic than a model.

e.g. a Validation library would be called/used from many different models, for instance from a User model and a Customer model which both need to access the Validation methods but are in themselves specific models. In that example my controller would be instantiating instances of my Customer and User models, and those in themselves would create an instance of the Validation library when necessary.

You seem to have it the other way round, where the methods in the Auth library are accessing/passing through to the Auth model. This confused me for a bit and I was just wondering why you chose to do it this way (maybe my understanding of models/libraries is incorrect?).

Second, why did you choose to write your own db->set() method instead of using CI's Active record? I mean, I know that both your set() and insert() methods are passed straight into CI's Active Record, but whereas I can see why you created the insert() (so that it would return true/false for a *single* insert in one call), I don't understand how your set() is functionally any different from CI's set() (aside from reversing the order of arguments).

Thanks!