And I now fear that if pricing changes again in a different direction in the future, the optimization we're doing now will also become useless. In effect, I'm trying to "game the system" - doing whatever I can to meet the free quota, until my app starts generating some revenue. And I suppose doing things like that does sometime bite in the future. In your case, your past effort may seem to have gone waste, given new pricing schemes, but it probably still goes a long way for future scalability.
On Fri, Sep 9, 2011 at 5:11 PM, Steve <unetright.thebas...@xoxy.net> wrote: > That is a good idea, thank you. > > It's still irritating that after many app refactorings and entity > migrations to optimize to the previous GAE flaming hoops and best practices > now again I need to convolute the program with more contortions. At one > time I thought one of GAE's best features was its straight-forward APIs and > programming style. It's as if the Python runtime didn't have enough bondage > and discipline so Google had to add it back in somehow. > > --Steve > > -- > 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/-/AZS6zU6FO_AJ. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
