Re: [google-appengine] X-AppEngine-Country at times returns ZZ
On Wed, Nov 5, 2014 at 12:27 AM, Irene wrote: > I m using X-AppEngine-Country to get client country but some times its > returning ZZ . Is there any way to get the exact country code for each and > every request. > As Satyanarayana said, "ZZ" is code for unknown country. You might want to star this issue to follow up: https://code.google.com/p/googleappengine/issues/detail?id=5296 But if you want to try geolocating the IP address using different sources, you can try using a proxy service such as Cloudflare: https://support.cloudflare.com/hc/en-us/articles/200168236-What-does-CloudFlare-IP-Geolocation-do- or an API: http://freegeoip.net/ - -Vinny P Technology & Media Consultant Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"
And how are you?
The GCP Live event was telling the story around the continuum the Google
Cloud Platform now provides from PaaS to IaaS.
You have GAE and with Managed VMs (combined with Autoscaler) you have GAE
2.0 in the PaaS category. The GAE 1.0 docker images for Java/Php/Python
can be deployed on Managed VMs if you wanted to, and when you want to
customize that image ("I want Java 8"), okay, now you can.
You need to run certain software on cloud servers, go with GCE (servers,
disks, load balancers, etc.) in the IaaS category.
You want something in the middle, go with GKE (Google Containers Engine).
You can deploy the Docker items for Managed VMs to GKE, but if you want to
use features like traffic splitting, etc. then you want to use Managed VM.
Depends on your needs, your choice now.
I try to start in the PaaS section until I need to get out of it due to
certain technical requirements. But excited to have all these choices
along the PaaS to IaaS spectrum.
rock on,
hardwick
On Wednesday, November 5, 2014 6:43:44 PM UTC-5, Doug Anderson wrote:
>
> I don't think there's any reason to migrate existing apps unless App
> Engine no longer satisfies your requirements. I don't see App Engine going
> away... you just need to set your expectations of the platform accordingly
> (don't expect bugs to get resolved unless you have a paid support plan,
> don't expect earth shattering new services/features, etc).
>
> On Wednesday, November 5, 2014 3:31:40 PM UTC-5, Emanuele Ziglioli wrote:
>>
>> Thank you everyone for your insights, very interesting.
>>
>> What do you guys think it's the way forward?
>> Are you going to migrate your GAE apps to to Managed VMs, with Docker and
>> the gcs command line tools?
>>
>> Also, is the Datastore still a valid option?
>> I wish BigQuery just worked natively with it...
>>
>> Thanks
>> Emanuele
>>
>>
--
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 group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"
I don't think there's any reason to migrate existing apps unless App Engine no longer satisfies your requirements. I don't see App Engine going away... you just need to set your expectations of the platform accordingly (don't expect bugs to get resolved unless you have a paid support plan, don't expect earth shattering new services/features, etc). On Wednesday, November 5, 2014 3:31:40 PM UTC-5, Emanuele Ziglioli wrote: > > Thank you everyone for your insights, very interesting. > > What do you guys think it's the way forward? > Are you going to migrate your GAE apps to to Managed VMs, with Docker and > the gcs command line tools? > > Also, is the Datastore still a valid option? > I wish BigQuery just worked natively with it... > > Thanks > Emanuele > > -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"
Thank you everyone for your insights, very interesting. What do you guys think it's the way forward? Are you going to migrate your GAE apps to to Managed VMs, with Docker and the gcs command line tools? Also, is the Datastore still a valid option? I wish BigQuery just worked natively with it... Thanks Emanuele -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: "One senses GAE is just not a major priority for Google"
+1 Doug. I hope someone from google reads these messages. To move away from GAE to Compute Engine based systems will require lot of rewiring in many projects. Hopefully things wont come to that. On Wed, Nov 5, 2014 at 10:53 PM, Doug Anderson wrote: > I've certainly felt that App Engine hasn't been a significant priority for > Google for quite some time. Legitimate bug reports can go unacknowledged > for years. The velocity of change has been largely centered around > increased language support rather than significant service expansion and/or > bug fixes. It comes across as "We've invested in this GAE ecosystem. What > can we do to get more people to adopt it before we invest too much more?" > So rather than expand/enhance the services themselves they focused on > additional language bindings. Now, it feels like they've realized even the > additional language bindings weren't enough. > > The recent announcements around the Google Cloud Platform Live event make > it pretty clear that Google realizes it can't tackle the cloud alone. With > Kubernetes/Google Container Engine, bitnami, and Managed VMs for App Engine > it's clear Google is building around Google Compute Engine in much the same > way Amazon built AWS around EC2. I'm sure at some point all App Engine > instances will be migrated to Compute Engine. Other than VMs for App > Engine going beta I don't think there were any GAE service expansion > announcements at the Live event. So this new, open, cooperate, run > anything approach is the shiny new toy in the Google Cloud group (I don't > see this as a bad thing... just more evidence that legacy GAE core services > are NOT a priority). > > There's A LOT to like about GAE... I REALLY like the dynamic image serving > service, IP geo-location with every request, ndb w/ integrated auto > memcaching, and NOT having to worry about OS and web server > configuration!!! GAE's ease of use is an area where Google actually has an > advantage over AWS. But as a developer there's an uneasy feeling about > adopting a proprietary platform like GAE when you see legitimate bugs > remaining stale for years at a time and the rate of service > expansion/enhancement seems almost stagnate. All the new announcements > seem to be pointing somewhere beyond legacy GAE which just reinforces the > uneasy feeling. > > - Doug > > > On Tuesday, October 28, 2014 5:11:15 PM UTC-4, Emanuele Ziglioli wrote: >> >> I would find hard to disagree: >> >> *IBM, Google, and Oracle are all equally at pains to deliver a message >>> that makes them uniquely attractive. In this regard, Google's inability to >>> recover from the botched roll-out of Google App Engine (GAE) will surely go >>> down as one of the oddest business cases. It launched the product with >>> great fanfare. But developers who flocked to it initially found a difficult >>> platform that supported only a subset of Java and a very old version of >>> Python. Moreover, the interfaces to the proprietary database were poorly >>> thought out, so that almost everything in GAE required platform-specific >>> code-arounds. While GAE has improved in a limited sense since then, Google >>> has not done what Microsoft did — revamp the product from top to bottom to >>> make it easy to use. Nor has it leveraged its natural connection to >>> developers. One senses GAE is just not a major priority for Google.* >> >> >> http://www.drdobbs.com/cloud/whose-cloud-will-you-use/240169229 >> >> >> -- > 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 group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/d/optout. > -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: "One senses GAE is just not a major priority for Google"
I've certainly felt that App Engine hasn't been a significant priority for Google for quite some time. Legitimate bug reports can go unacknowledged for years. The velocity of change has been largely centered around increased language support rather than significant service expansion and/or bug fixes. It comes across as "We've invested in this GAE ecosystem. What can we do to get more people to adopt it before we invest too much more?" So rather than expand/enhance the services themselves they focused on additional language bindings. Now, it feels like they've realized even the additional language bindings weren't enough. The recent announcements around the Google Cloud Platform Live event make it pretty clear that Google realizes it can't tackle the cloud alone. With Kubernetes/Google Container Engine, bitnami, and Managed VMs for App Engine it's clear Google is building around Google Compute Engine in much the same way Amazon built AWS around EC2. I'm sure at some point all App Engine instances will be migrated to Compute Engine. Other than VMs for App Engine going beta I don't think there were any GAE service expansion announcements at the Live event. So this new, open, cooperate, run anything approach is the shiny new toy in the Google Cloud group (I don't see this as a bad thing... just more evidence that legacy GAE core services are NOT a priority). There's A LOT to like about GAE... I REALLY like the dynamic image serving service, IP geo-location with every request, ndb w/ integrated auto memcaching, and NOT having to worry about OS and web server configuration!!! GAE's ease of use is an area where Google actually has an advantage over AWS. But as a developer there's an uneasy feeling about adopting a proprietary platform like GAE when you see legitimate bugs remaining stale for years at a time and the rate of service expansion/enhancement seems almost stagnate. All the new announcements seem to be pointing somewhere beyond legacy GAE which just reinforces the uneasy feeling. - Doug On Tuesday, October 28, 2014 5:11:15 PM UTC-4, Emanuele Ziglioli wrote: > > I would find hard to disagree: > > *IBM, Google, and Oracle are all equally at pains to deliver a message >> that makes them uniquely attractive. In this regard, Google's inability to >> recover from the botched roll-out of Google App Engine (GAE) will surely go >> down as one of the oddest business cases. It launched the product with >> great fanfare. But developers who flocked to it initially found a difficult >> platform that supported only a subset of Java and a very old version of >> Python. Moreover, the interfaces to the proprietary database were poorly >> thought out, so that almost everything in GAE required platform-specific >> code-arounds. While GAE has improved in a limited sense since then, Google >> has not done what Microsoft did — revamp the product from top to bottom to >> make it easy to use. Nor has it leveraged its natural connection to >> developers. One senses GAE is just not a major priority for Google.* > > > http://www.drdobbs.com/cloud/whose-cloud-will-you-use/240169229 > > > -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: X-AppEngine-Country at times returns ZZ
*App Engine determines this code from the client's IP address"*. So they actually look at an IP from where the connection was made. 'ZZ' is often used to denote 'Unknown or unspecified country' If your using Proxy, Since proxy sits between the client and AppEngine, AppEngine sees connections coming from proxy IP. On Wednesday, 5 November 2014 11:57:02 UTC+5:30, Irene wrote: > > I m using X-AppEngine-Country to get client country but some times its > returning ZZ . Is there any way to get the exact country code for each and > every request. > > Thanks! > -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] X-AppEngine-Country at times returns ZZ
*App Engine determines this code from the client's IP address"*. So they actually look at an IP from where the connection was made. 'ZZ' is often used to denote 'Unknown or unspecified country' If your using Proxy, Since proxy sits between the client and AppEngine, AppEngine sees connections coming from proxy IP. On Wed, Nov 5, 2014 at 11:57 AM, Irene wrote: > I m using X-AppEngine-Country to get client country but some times its > returning ZZ . Is there any way to get the exact country code for each and > every request. > > Thanks! > > -- > 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 group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/d/optout. > -- Thank you Satya -- 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 group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
