CodeIgniter中Libraries与Drivers的差异及存储疑问解析

Hey there, let's break down the key distinctions between Libraries and Drivers in CodeIgniter—this is something that trips up a lot of folks when they're first working with the framework:

1. Architectural Dependency #

• Libraries: Standalone, self-sufficient components. They don't rely on any special parent classes or framework-specific structures to function. You can call them directly once loaded, and they handle a complete, independent set of tasks (like sending emails with the Email library or managing sessions with Session).
• Drivers: These are specialized extensions tied to a parent library. They must inherit from CodeIgniter's base CI_Driver class and are always built to extend the functionality of a core parent library. For example, the Cache library has multiple drivers (File, Redis, Memcached) that all follow the same interface but implement caching in different ways.

2. Storage & Loading Logic #

• Libraries:
  • System-provided libraries live in system/libraries/
  • Custom libraries go in application/libraries/
  • Load them directly with $this->load->library('library_name'), and you can immediately use their methods via $this->library_name->method().
• Drivers:
  • System drivers are nested inside their parent library's directory: system/libraries/[Parent_Library]/drivers/ (e.g., system/libraries/Cache/drivers/)
  • Custom drivers need to be placed in application/libraries/[Parent_Library]/drivers/ (match the parent library's directory structure)
  • Loading requires two steps: first load the parent driver library with $this->load->driver('parent_library'), then access the specific driver via the parent instance (like $this->cache->redis->get('key')). You can't load a driver directly on its own.

3. Functional Purpose #

• Libraries: Designed to handle a broad, complete feature set. They're general-purpose tools that solve a specific type of problem (e.g., form validation, image manipulation).
• Drivers: Focus on providing alternative implementations of the same feature. They let you swap out how a parent library works without changing your application code. For example, if you switch from using the File cache driver to the Redis driver, you only need to adjust which driver you call—all the cache method names (like save(), get()) stay the same.

4. Extension Approach #

• Libraries: You can extend or override system libraries by creating a class with the same name in application/libraries/, or create a subclass that inherits from the system library to add new features.
• Drivers: To extend or add a custom driver, you need to create a class that follows the parent library's interface, place it in the correct drivers subdirectory, and then it becomes available via the parent library instance. You can't use a driver independently of its parent.

内容的提问来源于stack exchange，提问作者nyedidikeke