Or better, dont change pricing for existing customers. Change it only for new customers and apps.
On Sep 1, 1:31 pm, Angke <manc...@gmail.com> wrote: > +1984 > > On Sep 1, 9:28 am, bFlood <bfl...@spatialdatalogic.com> wrote: > > > > > > > > > +100 > > > On Sep 1, 12:23 pm, Mark Bucciarelli <mkb...@gmail.com> wrote: > > > > i assume you guys must be getting some serious > > > pressure from upper management to start making > > > some money here. > > > > but asking us to: > > > > (1) convert to HR to get the SLA and > > > > (2) convert to multithreading > > > > is asking a lot. asking it in a short time frame is > > > not realistic, especially for someone running a > > > large app in production with many users. > > > > threads suck. they introduce a ton of > > > complexity---race conditions that are hard > > > to imagine, and mostly impossible to reproduce > > > in a reliable way during unit testing. > > > > is there any possibility you can delay the price > > > increase until after 2.7 is out and you have > > > published some good docs on how to safely > > > move to multi-threading and HR? > > > > thanks, > > > > m -- 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.
