call lua_gc() for incremental garbage collection. Likely there is to tune this at...

[redis.git] / src / SCRIPTING.txt

diff --git a/src/SCRIPTING.txt b/src/SCRIPTING.txt
index 64d47580176e264b01f0718a648cc31c3b8bc1e8..31dd6a32452cbe9db7762a43f8e604b72f47db00 100644 (file)
--- a/src/SCRIPTING.txt
+++ b/src/SCRIPTING.txt
@@ -1,4 +1,31 @@
+Documentation:
+
+    http://antirez.com/post/scripting-branch-released.html
+
 TODO:
 
-    redis('get',1) => crash
-    Fix multi bulk replies, redis('lrange', ...)
+    MULTI/EXEC/...: should we do more than simply ignoring it?
+
+    Prevent Lua from calling itself with redis("eval",...)
+
+    Implement log() function, and define REDIS_WARNING, REDIS_NOTICE, ...
+
+    SCRIPT FLUSH or alike to start a fresh interpreter.
+
+    Max exection time for scripts, even pretty high, but in order to
+    prevent that an instance gets completely freezed by error.
+    Hint: Use a debug hook for this (lua_sethook() with LUA_MASKCOUNT).
+
+Blog post TODO:
+
+    Explain that for now this is just an experiemnt and there is no way to
+    tell if this will ever enter Redis stable, but that since it is pretty
+    self contained it is trivial to rebase with the unstable branch.
+
+    Explain how replication / AOF mix with scripting and why it is this way,
+    and that scripts should be written to don't depend from timing or other
+    external events if you want to use AOF / replication.
+
+    Show how fast it is!
+
+    Mention that dynamically generated scripts are not a good idea.