Hi Kaan, Thanks for your quick reply and your feedback on this forum. It's truly an open question to what extent the complication of network programming can be reduced when understanding of how to implement more complex solutions using the basic building blocks available is needed. We certainly wouldn't want to design a quite specific easing algorithm and force that on users when we could instead leave them a more malleable basis on which to build whichever solution they deem best. Regardless, this really comes down to different attitudes to programming and software design, and shouldn't be a block in our discussion. As I mentioned, you shouldn't hesitate to make a feature request if you feel as though you'd like some more complex functionality to be available as a config-file option.
As to your comment on the activity in the public issue tracker, rest assured that we're actively doing triage and solving issues day-in and day-out. The issue is, we need to perform this based on some kind of priority, which is based partly on the number of users starring the issue, along with several other factors. The issue you created is only visible to Googlers and yourself since it was tagged with "Type-Production", and so not having been starred by anybody else, would not be picked up first as we triage the highest-priority issues. I hope you'll understand that we do have to focus on issues with many people reporting first of all, although eventually you will see action on your thread. Since I think you didn't mean to use the private "Type-Production" ACL for this issue, and it doesn't contain any information private to you, I've gone ahead and fixed the tags on the issue, and it is now visible to other users to star if they have the same issue. For now, as an aside related to the public issue tracker thread you linked, I'll note that JPEG files can, depending on several image factors, be larger than their sibling GIF image <http://www.bricklin.com/webphotojournals/gifvsjpeg.htm>. This might be causing the API *response *size to break the 32MB limit <https://cloud.google.com/appengine/docs/python/images/?hl=en&csw=1#Python_Quotas_and_limits>. This is just conjecture and reliably reproducing a failing example where both the input and output are below the size limit would be a good way to make sure this issue can be handled as smoothly as possible. Overall, I hope I've helped put you at ease with regard to how we handle issues and the new focus on community support going forward. I don't think you should need to resort to "public campaigning" in the future if you make the best use of the appropriate forum for the appropriate issue. In a few words, you could remember "google groups for discussion, public issue tracker for platform or issues, stackoverflow for code issues", with the understanding that it might not be always possible to determine whether one issue should be in the public issue tracker or stackoverflow, but doing our best nonetheless to choose the one that seems most appropriate. We're dedicated to the task of helping as many people as much as we can, and though we won't always be active on every new issue or question as soon as it pops up, you will see us active, and with very good responsiveness once we do sit down to take on a particular issue. Sincerely, Nick On Wednesday, May 27, 2015 at 11:07:14 AM UTC-4, Kaan Soral wrote: > > Hi Jesse, Nick > > As a small reply to the technical issues, my main complaint is the > complication of things, yes I could develop the easing logic myself, > however I shouldn't - as for the limits, for non-users they seem like > simple limits, yet for a user, these limits block the scalability of the > app and they are only observable through experimentation, which means > building something and discovering the cold fact that it doesn't scale > > I see now that a lot changed recently and the support/support efforts > really improved, your replies are proof enough for this, thank you > > When I experience an issue again, I will give the public issue tracker > another chance: https://code.google.com/p/googleappengine/issues/list > > In the meantime, as a very small suggestion, it would be great if the > public issue tracker issues are visited and cleaned, it would show users > like me that things are changing and re-ignite the momentum that we once had > For example, this was a small images service issue that I had, the > operation is within limits but It used to fail, I never got a reply: > https://code.google.com/p/googleappengine/issues/detail?id=10301 - There > are many more issues like these that I forget about, this is why when I > experience a problem, I resort to public campaigning instead of simple > reporting > > Anyway, thanks once again, > Kaan > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/24e5db8e-4757-4cf0-94d8-a7d37105d881%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
