If you would like you can send me $250 a month and I’ll take your call 24/7.
I’ll even pretend I care about your downtime, and that “we” are working to
resolve the issue.
 
This is 5x the price of Amazon, and ½ the price of google, but I’ll be more
responsive than Google, and less of a jerk than Amazon.  In either case the
fixes for your issues will be resolved in the same time frame as everyone
else because for the most part no one knows which physical machines your
stuff is running on or how to move it, if they are in fact acting weird.
 
Issue 2. Run on production in a test instance… 

Issue 3. Hybrid with Amazon to do reverse proxy, That way I can sell you
another $250 a month support contract for them as well J
 
All kidding aside, I don’t think support will increase your uptime. It might
help with your TLS/SSL issues. I often think the Dev Server has bugs
intentionally. I think complaining about them encourages them to leave them
in so they know how many people are running it.
 
From: [email protected]
[mailto:[email protected]] On Behalf Of Jonathan Layes
Sent: Monday, January 16, 2012 7:28 AM
To: [email protected]
Subject: [google-appengine] Potentially blocking issues as we near
production: TLS/SSL, POST/PUT chunked encoding, support options
 
Hi folks,

Our team has been developing a product for about a year on app engine (Java)
and we've been very happy with it as a development platform. However, I have
now reached a point where I need to decide if we can stay on GAE as we move
closer to production. At the moment, there are three issues that could block
us moving to production on GAE:

1) TLS/SSL support for custom domains: This has been asked by many others
and I know Google's policy is not to provide release dates. However, this
really is a showstopper for us. We cannot move to production on GAE without
TLS support on our domain. I applied for the TLS Trusted Tester program
about two months ago but I have not heard anything in response. Is there any
way to determine where a Trusted Tester application is in the queue?

2) Chunked encoding on PUT or POST body: For some reason, the development
server in Java does not accept a chunked transfer encoding for PUT or POST
requests (it returns 411 length required errors). Fortunately, the GAE
frontend does not suffer from this limitation; the problem only occurs in
development (and we have workarounds). However, given that the Python folks
also report this problem in development (see
http://code.google.com/p/googleappengine/issues/detail?id=129), I would feel
more comfortable moving to production on GAE if someone at Google could
state that you intend to continue supporting chunked transfer encoding for
PUT/POST requests. Our application cannot determine the length of the POST
request body in advance and relies on chunked encoding. The HTTP 1.1
specification requires support of chunked encoding and so I'm not sure why
the development servers fail to support a chunked transfer encoding.

3) Support options: (Not necessarily a showstopper but an important
consideration) $500/month is rather pricey for a one-model-fits-all
solution, especially when the response times are 24 hours and limited to
weekdays. Compare that to even the Bronze $49/month for Amazon AWS (12 hour
turnaround any day of the week) and, at least on paper, AWS appears to have
both better and more affordable support options. Are there plans to provide
other support plans in the future?

Thanks, Jonathan
-- 
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/-/mEbSHRP1TJsJ.
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.

Reply via email to