I just want to say that I echo Reinier's sentiment: I don't really trust any
JSON-safe-ifying regex unless it comes with a formal proof (which doesn't
seem inconceivable -- anyone know of one?). How many times have you heard
about a security hole (usually x-site scripting) of the form "our HTML or
Seems to me that it wouldn't be that hard to build a simple lexical
scanner and recursive decent parser for JSON that avoids eval
altogether. For most JSON payloads its performance probably wouldn't
matter.
Doing it with just a single regex test seems unlikely. JSON is context
free, not regular,
Author: [EMAIL PROTECTED]
Date: Mon Sep 1 16:25:13 2008
New Revision: 3599
Added:
wiki/RpcAuth.wiki
Log:
Created wiki page through web user interface.
Added: wiki/RpcAuth.wiki
==
--- (empty file)
+++ wiki/RpcAuth.w
Author: [EMAIL PROTECTED]
Date: Mon Sep 1 16:33:02 2008
New Revision: 3600
Added:
wiki/RpcByInterface.wiki
Log:
Created wiki page through web user interface.
Added: wiki/RpcByInterface.wiki
==
--- (empty file)
+++
Author: [EMAIL PROTECTED]
Date: Mon Sep 1 16:53:18 2008
New Revision: 3601
Added:
wiki/RpcDirectEval.wiki
Log:
Created wiki page through web user interface.
Added: wiki/RpcDirectEval.wiki
==
--- (empty file)
+++ wi
Here are three API design docs to address some common issues with the
GWT RPC system.
An API for passing an authentication token or session information
within RPC payloads, without having to add additional parameters to
each method or playing around with HTTP headers:
http://code.google.com/p/g
