I think if you care that much about your privacy and your code, then don't put it on someone else's hardware, be it google, amazon, slice host or anyone else for that matter.
T On Apr 4, 3:12 pm, Portos <[email protected]> wrote: > of course they sould, specially to paying customers. I think that that > kind of care and politeness is what they are paying for. My point is > that looking in someones code is like breaking in your house. My code > is my territory and I like to know when I am beeing spied (whatever > the spie's good reason is). Otherwise if you consider that my code is > as much my property as my car of my house I should have the right of > choosing to be inspected or to have my app shutted down. > > (sorry for my english) > > On Apr 3, 8:22 pm, Xavier Mathews <[email protected]> wrote: > > > Well We Are using Their SDK Etc....And There Is A Privacy Policy On Content > > storing and processing! If they have over 100 developers who codes > > are causing problems to the system and causing instable then the easiest way > > for them to fix it is to look at your code and fix it. You Are saying the > > should come in contact with every one who's code is out of order and try > > and communicate effectively to try and fix it. Google does not have the time > > and that would just be to much confusion! As long as they do not tamper with > > the code i see no problem of them looking at it! > > > "Sent From Sony Slim-Line PSP" > > > Xavier A. Mathews > > Web-Developer > > > Sent from Chicago, Illinois, United States > > > On Thu, Apr 2, 2009 at 7:30 PM, Scott <[email protected]> wrote: > > > > I'm another developer with concerns about the privacy policy. > > > > "Content. Google App Engine stores, processes your application source > > > code and content in order to provide the service to you." > > > > The fact that the above isn't even grammatically correct doesn't do > > > much for my confidence. > > > > Marzia - you mention that google employees might look at the code "if > > > your application is causing system wide instability". Is that really > > > necessary? Could you not just shut it down? If you were interested in > > > determining how it caused instability in the face of controls you have > > > put in place to prevent that situation, could you not work with the > > > customer to e.g. isolate the problematic code so that you wouldn't > > > have to get involved with the real application? Would you notify the > > > customer and give them the opportunity to pull the code before you get > > > involved with it? > > > > I am curious about your answers, and I do believe in the good > > > intentions of the app engine team and Google in general. But also, and > > > as Colin said, it would be excellent to get that kind of clear > > > language into the legal documents. Data privacy concerns are a major > > > barrier to cloud adoption in business (for anyone with doubts, there's > > > this great tool called Google Search you may want to try). The kind of > > > clear language you've used here would really help to mitigate that > > > issue, were it legally binding, or even prominently displayed (in the > > > FAQ or similar). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
