Simple flat file database backend. Creates a file per key.

No locking is done within this backend yet.

Confiugration options:

None

• todo: Implement proper locking

Located in /midcom/services/cache/backend/flatfile.php (line 23)

midcom_services_cache_backend
   |
   --midcom_services_cache_backend_flatfile

string $_dirname = null (line 31)

The full directory filename.

• access: private

Inherited Variables

Inherited from midcom_services_cache_backend

midcom_services_cache_backend::$_auto_serialize
midcom_services_cache_backend::$_cache_dir
midcom_services_cache_backend::$_config
midcom_services_cache_backend::$_name
midcom_services_cache_backend::$_open_for_reading
midcom_services_cache_backend::$_open_for_writing

Constructor midcom_services_cache_backend_flatfile (line 36)

The constructor is empty yet.

midcom_services_cache_backend_flatfile midcom_services_cache_backend_flatfile ()

exists (line 111)

void exists (mixed $key)

---

Redefinition of:

midcom_services_cache_backend::exists()

Checks, wether the given key exists in the Database. If the data store has not yet been opened for reading, it will be opened automatically prior to the call, and closed automatically again afterwards.

get (line 59)

void get (mixed $key)

---

Redefinition of:

midcom_services_cache_backend::get()

Get the data accociated with the given key. If the data store has not yet been opened for reading, it will be opened automatically prior to the call, and closed automatically again afterwards.

put (line 70)

void put (mixed $key, mixed $data)

---

Redefinition of:

midcom_services_cache_backend::put()

Store the given key/value pair, any existing entry with the same key has to be silently overwritten. If the data store has not yet been opened for writing, it will be opened automatically prior to the call, and closed automatically again afterwards.

remove (line 88)

void remove (mixed $key)

---

Redefinition of:

midcom_services_cache_backend::remove()

Delete the data with the given key from the database. Deleting non existant keys should fail silently. If the data store has not yet been opened for writing, it will be opened automatically prior to the call, and closed automatically again afterwards.

remove_all (line 93)

void remove_all ()

---

Redefinition of:

midcom_services_cache_backend::remove_all()

Drops the entire database and creates an empty one.

_on_initialize (line 45)

This handler completes the configuration.

void _on_initialize ()

---

Redefinition of:

midcom_services_cache_backend::_on_initialize()

Backend initialization

Inherited Methods

Inherited From midcom_services_cache_backend

midcom_services_cache_backend::midcom_services_cache_backend()
midcom_services_cache_backend::close()
midcom_services_cache_backend::exists()
midcom_services_cache_backend::get()
midcom_services_cache_backend::initialize()
midcom_services_cache_backend::open()
midcom_services_cache_backend::put()
midcom_services_cache_backend::remove()
midcom_services_cache_backend::remove_all()
midcom_services_cache_backend::shutdown()
midcom_services_cache_backend::_check_cache_dir()
midcom_services_cache_backend::_close()
midcom_services_cache_backend::_exists()
midcom_services_cache_backend::_get()
midcom_services_cache_backend::_on_initialize()
midcom_services_cache_backend::_on_shutdown()
midcom_services_cache_backend::_open()
midcom_services_cache_backend::_put()
midcom_services_cache_backend::_remove()
midcom_services_cache_backend::_remove_all()