Hi Jonathan, There are a few recent threads in the groups with similar questions. You might be able to come up with something more clever, but you'll likely wind up using eval. Keep the potential security risks in mind -- anyone who uploads code will have full access to your datastore, memcahce, etc....
Robert On Fri, Jul 22, 2011 at 16:40, Jonathon Broughton <[email protected]> wrote: > we are building a customisable dashboard/widget type interface that can > include any number of 'preinstalled' widgets. > i am looking into the best logic for how to store the assorted files that go > into making a gadget. most of it is straightforward, but i need to establish > the best way of 'installing' future widgets and any associated backend code > that may be associated with them – ideally this is not by repeated > deployment > if one assumes a w3c widget spec object (or opensocial whatever) that is a > package of files with a manifest that also were to include arbitrary backend > code as well as the views and frontend stuff, would storing backend code in > datastore and pulling it out at runtime for eval() be efficient? > jonathon > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/ZPjjUusdDyUJ. > 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. > -- 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.
