The caja server now only provides proxying for external script tags and style tags; it has to do some simple wrapping, but nothing like the complete code transformation that the original server did. If you're disallowing external scripts and styles, the caja server is merely the location of the js files.
On Fri, May 2, 2014 at 12:55 PM, Helen Wu <[email protected]> wrote: > Thanks for the fast reply! But, I'm a bit confused how this happens. I have > caja.js in my project, but from the documentation it still seems to have to > call a caja server to load the cajoled content? Am I going about this wrong? > > On Friday, May 2, 2014 11:43:13 AM UTC-7, Kevin Reid wrote: >> >> On Fri, May 2, 2014 at 11:23 AM, Helen Wu <[email protected]> wrote: >>> >>> I want to do the same thing as mentioned here: >>> https://groups.google.com/forum/#!msg/google-caja-discuss/ZEF9IupkJnQ/jyJTFuEbrwEJ >>> >>> However, I noticed that the post is a bit outdated now and some of the >>> files that are mentioned don't exist anymore. Is there a better/more correct >>> way to do this now? >> >> >> Caja no longer uses a server to rewrite content, so there is no "cajoling" >> step; instead, all needed operations are performed in the client JS. >> >> This ("ES5 mode") is much faster overall than the old way even with >> precajoling. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Google Caja Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Mike Stay - [email protected] http://www.cs.auckland.ac.nz/~mike http://reperiendi.wordpress.com -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
