Thanks Wolfram for sharing this valuable insight and experience! This
really helps! To update, we got it working with Rhino now. Just wondering
if GAE Team could update on this much debated issue.
On Monday, March 30, 2015 at 2:51:22 PM UTC+5:30, Wolfram Gürlich wrote:
>
> Even though I'm not on the GAE team I can say that Rhino works just fine
> on GAE. And even if GAE/J had built-in Javascript support, that would come
> out as Rhino anyway as this is the default engine for JDK1.7.
> Also server-side precompilation ("optimization") works flawlessly. No
> classloading issues there.
>
> We experienced a performance issue though, when implementing host objects
> the "standard" way (by deriving from ScriptableObject). Rhino uses dynamic
> invocation in this case, which is painfully slow on GAE in general due to
> Java sandboxing and repeated security checks. When host objects are
> implemented the same way as built-in native objects are (by deriving from
> IdScriptableObject) then Rhino just flies.
>
> Regards,
> Wolfram
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/d08f1f7f-e915-405b-bb9e-0b14ddb80033%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
