summaryrefslogtreecommitdiff
path: root/doc/plugins/write
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-08-13 07:00:53 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-08-13 07:00:53 +0000
commit5b78246d11948e93f54ae32dd800e9adaf55a546 (patch)
treea37a55ffb52bd62177d69b4d39a13fa0d1095840 /doc/plugins/write
parent27c1595cec8606f44d2ec33989daca70cab7d22f (diff)
memoization for injected RPC functions is a very, very good thing
Diffstat (limited to 'doc/plugins/write')
-rw-r--r--doc/plugins/write/external.mdwn6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/plugins/write/external.mdwn b/doc/plugins/write/external.mdwn
index ca30dd229..3612dd9c3 100644
--- a/doc/plugins/write/external.mdwn
+++ b/doc/plugins/write/external.mdwn
@@ -78,6 +78,9 @@ example, make an RPC call to `inject`. Pass it named parameters "name" and
"Ikiwiki::rcs_update" and "call" is the RPC call ikiwiki will make whenever
that function is run.
+If the RPC call is memoizable, you can also pass a "memoize" parameter, set
+to 1.
+
## Limitations of XML RPC
Since XML RPC can't pass around references to objects, it can't be used
@@ -112,7 +115,8 @@ number of calls.
Injecting a replacement for a commonly called ikiwiki function
could result in a lot more RPC calls than expected and slow
eveything down. `pagetitle`, for instance, is called about 100 times
-per page build.
+per page build. Memoizing injected functions whenever possible is a very
+good idea.
In general, use common sense, and your external plugin will probably
perform ok.