design pattern question

[eluser]Pascal Kriete[/eluser]
I would consider libraries part of the business logic, so in that sense they're controller components.

More correctly though, I see them as part of the framework. MVC is an organizational pattern, but commonly used functions and classes still need to be seperated. A framework isn't just 'MVC', even if that is the buzzword these days.

In the core CodeIgniter uses other patterns as well. The loader is a singleton interface, form validation is a strategy pattern, the database drivers use an adapter pattern, etc. Design patterns aren't set in stone - it's not an all or nothing approach. It's useful to know a few by name, so you can quickly describe a design approach without going into the details. They work roughly the same in most higher level languages, so you can tell a Python guy how your PHP application accomplishes feature X using just two or three words. But then, I learned most of them from a javascript book, so what do I know .

Let's wait for Mr. Casburn to get here.