Not to hijack your thread, but it's a nightmare of mine too Appengine is really strong/weak because it includes everything in one place, if the code of another project was compromised, the person who stole the resources would have a hard time setting things up to run the stolen code, however for Appengine projects, the stolen code would be enough to spin many replicas
I think the wise/futuristic solution is to license the compiled/machine code to a person, much like university cheating prevention methods, this would prevent the usage of the code and raise flags to be interpreted by the team It would also make it really hard to give access to developers, as any leak would compromise the entire project A Scenario: Developer enters a coffee shop, someone easily grabs his/her laptop aaand it's gone Good thing I'm a lone developer like many here, if the above scenarios happen, it's nobody's fault but mine Out of curiosity, if you don't mind, what is your scenario? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
