es (neé modules) to have one service running on
> standard that works as your API frontend, and another service running on
> flexible that can handle the heavy lifting.
>
> On Wednesday, June 29, 2016 at 8:57:58 PM UTC-7, Robert King wrote:
>>
>> Sorry if this is harsh and
Sorry if this is harsh and correct me if i'm wrong.
I think google should take a stance on this. You can't just say "feel free
to file a feature request". Google should decide if endpoints make sense or
not and if not, apologies to existing developers using it & put a warning
in the
I agree with Jeff Schnitzer. I think google is afraid of the whole open
source docker thing gaining huge momentum and doesn't want to miss out so
they want to make that part of their foundation e.g. things like
kubernettes. They also want to make it easy for people to migrate from
other
Hi Jun,
Thanks so much for answering these questions - it's very helpful.
What does the additional frontend API layer do? What's the performance
impact?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group and
I found this related issue
here https://code.google.com/p/googleappengine/issues/detail?id=10017
On Thursday, 22 May 2014 17:46:16 UTC+12, Robert King wrote:
the link is /_ah/api/discovery/v1/apis/archivedash/v1/rpc?
fields=methods%2F*%2Fidpp=0
is for discovery - it's a google thing - i
Don't get me wrong - I absolutely love cloud endpoints - they speed up my
development time and simplify my code significantly.
Having said that, I'd really like to see some clarification from google.
Are endpoints intended to be high performance? I haven't once seen
mentioned in any google
also might be worth noting I'm using CORS on multiple app engine modules
etc. perhaps it's something to do with preflight requests?
http://monsur.hossa.in/2012/09/07/thoughts-on-the-cors-preflight-cache.html
On Sunday, 25 May 2014 20:53:15 UTC+12, Robert King wrote:
Don't get me wrong - I
:38 PM, Robert King
kingrob...@gmail.comjavascript:
wrote:
I'm running appstats but that request doesn't come through
(other api calls do come through on app stats)
That's fine.
For the other API calls, do they do largely the same work as the
problematic API endpoint, or do
, Robert King
kingrob...@gmail.comjavascript:
wrote:
for
examplehttp://stackoverflow.com/questions/23618638/google-cloud-endpoints-ah-api-discovery-v1-apis-myapi-v1-rpc-takes-half-a-minu
,
/_ah/api/discovery/v1/apis/archivedash/v1/rpc?fields=methods%2F*%2Fidpp=0
is often at times running
HI, is this possible? I tried searching app engine logs: path:/_ah/api.*
nothing came up obviously.
for
examplehttp://stackoverflow.com/questions/23618638/google-cloud-endpoints-ah-api-discovery-v1-apis-myapi-v1-rpc-takes-half-a-minu
,
I'm in NZ too and none of my domains are working!
On Wednesday, 12 March 2014 09:51:30 UTC+13, GregF wrote:
Yes - same issue here (NZ) on some networks. Great to hear I'm not the
only one. HELP!!!
On Wednesday, 12 March 2014 09:40:24 UTC+13, Tomas Adamek wrote:
Hi there
it seems like
A few hours ago most of our python app went down all requests were timing
out. (Our app has never been down before).
I checked https://code.google.com/status/appengine/ and it said
investigating for Memcache Python so they must have been having some
issues.
I'm not sure why there is a green
12 matches
Mail list logo
