I have at times experienced definite clock skews (I documented some up as
much a minute in the early stages.)
I personally think it is a mistake to design a solution that needs 5 sec
clock accuracy with appengine.
T
On Saturday, November 2, 2013 12:32:43 PM UTC+8, Vinny P wrote:
On Fri,
Hi! For my python google app engine app I'm relying on some functions being
picked up from external providers at l.macbay.dk
This has worked neatly for a year or so, but a couple of days ago appengine
simply stopped allowing fetch of this address not just returning Unable to
fetch URL. No
Vinny
Unfortunately python urlfetch does not have any cache bypass options that I
can see. I tried fetching from a different name for the same server, and
that didn't work. The server doesn't have anything funny in front of it
I have worked around it now by creating a specific ipv6 only
thanks, this is what I was looking for!
On Saturday, November 2, 2013 1:08:21 AM UTC+1, barryhunter wrote:
From
https://developers.google.com/appengine/docs/python/googlecloudstorageclient/#Python_Using_GCS_client_library_with_the_development_app_server
* You can use the client library with
How do you deal with ipv6 in app engine?
--
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 google-appengine+unsubscr...@googlegroups.com.
To post to this
By default, all appengine apps can be accessed over ipv6 (at least with
their appspot.com names). On the outbound side, you just do a
urlfetch.fetch on a URL which has a domain name that has an ipv6 address. I
don't know if they use a happy eyeballs approach -- I suspect not. I
suspect that
