Libraries or Models, favouritism?

[eluser]jbowman[/eluser]
For your controller why not

Code:

artist.php -> index() (my profile, if no session, redirect to registration or front page)
           -> blog($uid = "use_session")
           -> blog_entry($id)
           -> gallery($uid = "use_session")
           -> artwork($id)
.. more for adding comments on an artwork, comment the profile page, etc. etc.

Play with routes a little and get blog/add, blog/del, and blog/edit...

For models vs libraries, I'll give you an example of what I'm working on now.

I have an idea I'm working on where my site is going to authenticate against a jabber server, and also get profile information from there.

So, I grabbed an existing jabber library I found, and modified it a little to turn it into an acceptable library for CI.

Then I created a jabber.php in my config folder which includes the jabber host and port information (more information may be added later, all I need right now). This then gets autoloaded.

Now, I'm working on my jabber_model.php. Literally started on this last night. Currently is has 1 and a half methods. The jabber library is loaded in the constructor.

connect() - uses the information from the config file to connect to a jabber server
authenticate($username, $password) - calls the connect method to establish a connection to the jabber server, then authenticates based on passed variables.

So, as you can see, the library holds all the advanced protocol implementations, where as my model runs on top of that to plug in and retrieve information. By using generic methods like "connect, authenticate (you know I should change this to log in), logout, etc etc", I can swap out models under my controllers if I decide that I really don't want to use jabber after all.