proxy: restrict functions for lua config vs route

Also changes the way the global context and thread contexts are fetched
from lua; via the VM extra space instead of upvalues, which is a little
faster and more universal.

It was always erroneous to run a lot of the config functions from routes
and vice versa, but there was no consistent strictness so users could
get into trouble.

1 files changed, 2 insertions, 1 deletions

diff --git a/memcached.h b/memcached.h
index 3c54931..68d0ab0 100644
--- a/memcached.h
+++ b/memcached.h
@@ -719,7 +719,8 @@ typedef struct {
 #endif
     int napi_id;                /* napi id associated with this thread */
 #ifdef PROXY
-    void *L;
+    void *proxy_ctx; // proxy global context
+    void *L; // lua VM
     void *proxy_hooks;
     void *proxy_user_stats;
     void *proxy_int_stats;