> it's hard to do debugging when you have to re-upload the application every time you save your code... :-)
You just aren't used to working in an enterprise environment. I have been on products (Set Top Box) where a change to the code meant a 45 min compile, uploading the firmware to a TFTP server, Applying the update by pressing a button on the motherboard for 10 seconds during the powercycle of the STB, waiting 5 minutes for the firmware to install on the device and then launching the test series. Total time from code change to start of debug pass 1 hour. The solution is to make fewer code mistakes :-) From: [email protected] [mailto:[email protected]] On Behalf Of Mattia Landoni Sent: Friday, November 18, 2011 2:42 AM To: [email protected] Subject: [google-appengine] OpenID is awesome but I think I found two bugs First of all, I have to say that I love the idea that I can have millions of users without registration. It's just awesome. Even if probably I'll never have even 1000 users, but that's secondary. I found two problems with the behavior of the .federated_login() method of the User() object. These seem to be honest bugs, but I'd love to hear some expert feedback especially on the second one. I am using Python 2.7 but this could be a more general problem so I post here. The application can be found at http://shoushiling.appspot.com/. First, the method returns "None" when I use the SDK development server, which is a problem because I have to handle it separately, but more important, it's hard to do debugging when you have to re-upload the application every time you save your code... :-) Second, there is a problem on the actual App Engine. I had an entity with a UserProperty() which I called "name". I logged in with my Yahoo account to test it and it seemed to work. When I loaded a second page, the website behaved as if I had never been there. What happened was that the User() object evaluated once to my Yahoo email address, and once to my OpenID uri (dunno which one was first), so the website did not find me in the database the second time. I solved the problem by using the "federated_login()" method, which returns a string, and replacing the UserProperty with a StringProperty. This way I assume I have a unique identifier for every user no matter when they come from. Is that right? Thanks for listening Matt -- 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/-/9YlSor_H1YQJ. 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.
