(no commit message)
authorhttp://cgray.myopenid.com/ <cgray@web>
Fri, 10 Feb 2012 02:38:20 +0000 (22:38 -0400)
committeradmin <admin@branchable.com>
Fri, 10 Feb 2012 02:38:20 +0000 (22:38 -0400)
doc/todo/be_more_selective_about_running_hooks.mdwn [new file with mode: 0644]

diff --git a/doc/todo/be_more_selective_about_running_hooks.mdwn b/doc/todo/be_more_selective_about_running_hooks.mdwn
new file mode 100644 (file)
index 0000000..0c8e0b0
--- /dev/null
@@ -0,0 +1,20 @@
+[[!template  id=gitbranch branch=chrismgray/exclusive-hooks author="[[chrismgray]]"]]
+
+Sometimes plugins register a function with `hook`, but they only want
+the function called with the content that they know how to deal with.
+Normally, this means that they call `pagetype` first thing in the
+function, determine if they know how to deal with the content, and
+only do anything if they do.  
+
+This is a bit wasteful in itself, but for external plugins, it's
+really bad.  For functions like `scan` and `linkify`, where the entire
+page is sent back and forth over `stdout` and `stdin`, it really slows
+things down.  
+
+Thus, I propose that there be a new optional parameter to `hook` that
+tells it that the function should only be called for files whose type
+is the same as the id of the plugin calling `hook`.  I have called
+this parameter `exclusive` in my branch, but this might not be the
+best name.
+
+[[!tag patch]]