> Surely you talking about the closure *compiler*, not the closure *library* > here
Both. Nick's point (as I read it) is that you shouldn't be using one without the other, at least not in production, and my point is that there are valid situations in which you do want the library and not the compiler, and thus the availability of a fast, reliable and free host for the closure library files would be welcome. On Nov 8, 4:05 am, Barry Hunter <[email protected]> wrote: > 2009/11/7 hawkett <[email protected]>: > > > > >> What sort of runtime modification are you talking about? > > > A user changes a piece of javascript, or adds a piece of javascript - > > for the sake of the example lets assume the javascript is stored in > > the GAE datastore. Something that you get from javascript, and > > precisely because it doesn't require compilation, is the ability to > > press refresh on your browser and see the changes take effect. The > > only opportunity to compile here appears to be via the rest api - do > > you know if this api is suitable for GAE (e.g. execution timeouts > > could be a problem via URL Fetch?). > > Surely you talking about the closure *compiler*, not the closure *library* > here > > Admittedly my java is rusty, so dont know if you can use the provided > jar directly from (java!) appengine code. But downloadable as a 4mb > jar file so I would think that can be used on appengine. > > I don't know enough about the library to know if having it accessible > in a common location (like Django in python?), would actually be a > benefit. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
