limulus / mache Goto Github PK

Using null is more in line with the Node conventions.

This might look like the following:

var myMache = mache.create('/var/tmp/myapp/cache', myObjCreator)
// …
myMache.stats()  // → {"hits":1025, "misses":26, "errors":1, "objects": 23}

This is a better name for this method.

In the event of an object creation callback being asynchronous, it is possible for many requests for a newly-expired cache entry to trigger multiple object creations. We should attempt to prevent this.

Mache creation should look something like this:

var mache = require('mache')
  , path = require('path')

var templates = mache.create('./tempates', function (templatePath, templateData, updateMache) {
    var templateName = path.basename(templatePath)
    updateMache(new Template(templateName, templateData))
})

A mache instance should probably be an EventEmitter, which emits an event whenever a file has been deleted or changed. Maybe something like this:

templates.on('removal', function (template) {
    template.destroy()
})

Mache object getter should look something like this:

templates.get('PageHeader.html', function (header) {
    header.set('title', site.name() + ' — ' + article.title())
    header.render()
})

Something like the following:

myMache.on('error', function (err) { console.log(err) })

Currently, objects are never removed from a mache unless the file backing the object is removed. It might be useful to have mache make use of lru-cache, or perhaps any object with get, set and has methods.