[google-appengine] Re: How to set deadline for a PHP URL fetch?
Not sure what you mean by doesn't support fclose(). // This works fine. $fp = fopen(gs://sjl-test/song.ogg, r); var_dump(fstat($fp)); fclose($fp); Buut It looks like stream_get_meta_data doesn't return anything - I'll need to find out why. On Wednesday, 5 June 2013 11:13:38 UTC+10, 1moretime wrote: Thanks Vinny I'm trying to POST data to http://cx.xaa.cc/checksn.asp with gae php. It seems that my post request written in php closed in about 5 seconds, so i guess my request deadline was not set properly. GAE don't support fclose, so i don't know how to use stream_get_meta_data. Jason On Jun 5, 2:52 am, Vinny P vinny...@gmail.com wrote: Can you tell us what URL you're connecting to? The server may be slow or be difficult to resolve. I would suggest using *stream_get_meta_data* ( http://us3.php.net/stream_get_meta_data) to inspect the stream and see what exactly is going on - you'll get a more detailed error message. - -Vinny P Technology Media Advisor Chicago, IL My Go side project:http://invalidmail.com/ On Tuesday, June 4, 2013 6:51:47 AM UTC-5, 1moretime wrote: Hi, Stuart Thanks for your reply, I tried following code, but failed. code $data = http_build_query($data); $context = array(http= array( method = POST, content = $data, //header = Connection: keep-alive\r\n, //deadline = 60, // The deadline can be up to a maximum of 60 seconds for request handlers timeout = 30 // GAE requests have a 30-second deadline ) ); $context = stream_context_create($context); $result = file_get_contents($url, false, $context); /code Still got same warning message in gae logs. log PHP Warning: file_get_contents(..): failed to open stream: Request deadline exceeded in /base/data/home/apps/.php on line 93 /log Any suggestion? On Jun 4, 5:56 pm, Stuart Langley slang...@google.com wrote: set the timeout value in the http context to the number of seconds you want the deadline to be. On Tuesday, 4 June 2013 12:05:29 UTC+10, 1moretime wrote: Thanks, Dan I read that doc but PHP version not found. would you pls give some php code? On Jun 4, 4:16 am, Dan Holevoet danielholev...@google.com wrote: This is a great question for the App Engine Stack Overflow taghttp://stackoverflow.com/questions/tagged/google-app-engine, which also conveniently happens to have an answer http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-url...for you! Thanks, Dan On Mon, Jun 3, 2013 at 8:20 AM, 1moretime chengxia...@gmail.com wrote: URL Fetch overview says: You can set a deadline for a request, the most amount of time the service will wait for a response. By default, the deadline for a fetch is 5 seconds. The maximum deadline is 60 seconds for HTTP requests and 10 minutes for task queue and cron job requests. Now, how can i set deadline to 60-sec ? -- 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-appengi...@googlegroups.com javascript:. To post to this group, send email to google-a...@googlegroups.comjavascript:. Visit this group athttp:// groups.google.com/group/google-appengine?hl=en. For more options, visithttps:// groups.google.com/groups/opt_out. -- Dan Holevoet Google Developer Relations -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: How to set deadline for a PHP URL fetch?
Tried this as well.
file_get_contents(http://cx.xaa.cc/checksn.asp;);
var_dump($http_response_header);
array(11) {
[0]=
string(15) HTTP/1.1 200 OK
[1]=
string(17) Connection: close
[2]=
string(35) Date: Wed, 05 Jun 2013 07:35:38 GMT
[3]=
string(25) Server: Microsoft-IIS/6.0
[4]=
string(21) X-Powered-By: ASP.NET
[5]=
string(20) Content-Length: 1086
[6]=
string(23) Content-Type: text/html
[7]=
string(65) Set-Cookie: ASPSESSIONIDQCBBDSTC=DEEPGAHDFGIKBJAAOFHOGEPM;
path=/
[8]=
string(22) Cache-control: private
[9]=
string(36) X-Google-Cache-Control: remote-fetch
[10]=
string(17) Via: HTTP/1.1 GWA
}
On Wednesday, 5 June 2013 11:13:38 UTC+10, 1moretime wrote:
Thanks Vinny
I'm trying to POST data to http://cx.xaa.cc/checksn.asp with gae php.
It seems that my post request written in php closed in about 5
seconds,
so i guess my request deadline was not set properly.
GAE don't support fclose, so i don't know how to use
stream_get_meta_data.
Jason
On Jun 5, 2:52 am, Vinny P vinny...@gmail.com wrote:
Can you tell us what URL you're connecting to? The server may be slow or
be
difficult to resolve.
I would suggest using *stream_get_meta_data* (
http://us3.php.net/stream_get_meta_data) to inspect the stream and see
what exactly is going on - you'll get a more detailed error message.
-
-Vinny P
Technology Media Advisor
Chicago, IL
My Go side project:http://invalidmail.com/
On Tuesday, June 4, 2013 6:51:47 AM UTC-5, 1moretime wrote:
Hi, Stuart
Thanks for your reply,
I tried following code, but failed.
code
$data = http_build_query($data);
$context =
array(http=
array(
method = POST,
content = $data,
//header = Connection: keep-alive\r\n,
//deadline = 60, // The deadline can be up to a maximum
of 60 seconds for request handlers
timeout = 30 // GAE requests have a 30-second deadline
)
);
$context = stream_context_create($context);
$result = file_get_contents($url, false, $context);
/code
Still got same warning message in gae logs.
log
PHP Warning: file_get_contents(..): failed to open
stream: Request deadline exceeded in /base/data/home/apps/.php
on line 93
/log
Any suggestion?
On Jun 4, 5:56 pm, Stuart Langley slang...@google.com wrote:
set the timeout value in the http context to the number of seconds
you
want
the deadline to be.
On Tuesday, 4 June 2013 12:05:29 UTC+10, 1moretime wrote:
Thanks, Dan
I read that doc but PHP version not found.
would you pls give some php code?
On Jun 4, 4:16 am, Dan Holevoet danielholev...@google.com
wrote:
This is a great question for the App Engine Stack Overflow
taghttp://stackoverflow.com/questions/tagged/google-app-engine,
which also conveniently happens to have an
answer
http://stackoverflow.com/questions/2162115/how-to-set-timeout-for-url...for
you!
Thanks,
Dan
On Mon, Jun 3, 2013 at 8:20 AM, 1moretime chengxia...@gmail.com
wrote:
URL Fetch overview says:
You can set a deadline for a request, the most amount of time
the
service will wait for a response. By default, the deadline for
a
fetch
is 5 seconds. The maximum deadline is 60 seconds for HTTP
requests
and
10 minutes for task queue and cron job requests.
Now, how can i set deadline to 60-sec ?
--
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-appengi...@googlegroups.com javascript:.
To post to this group, send email to
google-a...@googlegroups.comjavascript:.
Visit this group athttp://
groups.google.com/group/google-appengine?hl=en.
For more options, visithttps://
groups.google.com/groups/opt_out.
--
Dan Holevoet
Google Developer Relations
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Count datastore reads for request
Thanks. BTW, I've found that my suspision was falsified. Anyhow, Loved your answer. Thanks On Wednesday, June 5, 2013 1:47:13 AM UTC+3, Matt Jibson wrote: You can use appstats to do that: https://developers.google.com/appengine/docs/python/tools/appstats Sorry for the previous link, thought it was on the go list. On Tue, Jun 4, 2013 at 11:08 AM, Yair Eshel guru...@gmail.comjavascript: wrote: I suspect one of my requests is taking more datastore calls then I set in my script. Any way to see datastore calls count, per request in my logs? -- 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-appengi...@googlegroups.com javascript:. To post to this group, send email to google-a...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/google-appengine?hl=en . For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
Chris just to clarify, this is *not* being deprecated is it? https://developers.google.com/appengine/docs/java/blobstore/overview#Writing_Files_to_the_Blobstore I sure hope not because I'm using it heavily in my apps. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Wordpress + AppEngine = PressEngine
more details about running Wordpress directly on GAE platform : https://developers.google.com/appengine/articles/wordpress best and happy coding.. @Mlaynes -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
Jon: The example you are pointing to is using two APIs. In java things under the package: com.google.appengine.api.blobstore are _not_ affected by this announcement. Things under the java package: com.google.appengine.api.files are affected by this announcement. We will be providing a migration guide for how to change code to use the Google Cloud Storage Client Libraryhttps://code.google.com/p/appengine-gcs-client/. This library is Preview as of 1.8.1 and as such is guaranteed to move to GA. Just to emphasize, this is a deprecation announcement, not a decommission. So your application will _not_ break with 1.8.1, but you should begin looking at how to port it to the new library. If you have questions about how to do this, feel free to create a thread on this group. On Wed, Jun 5, 2013 at 3:28 AM, jon jonni.g...@gmail.com wrote: Chris just to clarify, this is *not* being deprecated is it? https://developers.google.com/appengine/docs/java/blobstore/overview#Writing_Files_to_the_Blobstore I sure hope not because I'm using it heavily in my apps. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
Thanks for the clarification Chris. FWIW the blobstore files API (at least in Python) is also not very reliable (I've seen hangs as often as 1 in 10 file create-writes). So I'll be migrating my blob writes from blobstore to GCS as soon as possible! From my perspective the blobstore could be deprecated with GCS arrival EXCEPT the following functionality needs to be preserved: 1. The ability to upload files to GCS (of course you can already upload to GCS but this is currently done via the blobstore API). SOLUTION: gcs.create_upload_url() and gcs.GCSUploadHandler 2. The ability to serve and transform images via get_serving_url and Image. (again, you can already dynamically serve GCS images but it requires a call to blobstore create_gs_key). SOLUTION: Update the Images API to directly integrate with GCS everywhere blobstore does! With the above 2 solutions... I have no need for blobstore (although I'll have some code to migrate)! On Tuesday, June 4, 2013 10:20:49 PM UTC-4, Chris Ramsdale wrote: Jason, that is correct -- in a future release we are going to decommission the Experimental Google Cloud Storage API Functions. These APIs and their Experimental status are documented at the following links: - https://developers.google.com/appengine/docs/python/googlestorage/functions - https://developers.google.com/appengine/docs/java/googlestorage/overview Given this, we're moving the new Google Cloud Storage Client Libraryhttps://code.google.com/p/appengine-gcs-client/to Preview in the 1.8.1 release. Unlike Experimental features, Preview features are guaranteed to move to General Availability (GA). We encourage developers to start moving over to the new Cloud Storage Client Library as soon as possible. Information on getting started can be found at the open source project linked below. https://code.google.com/p/appengine-gcs-client/ Cheers, -- Chris Ramsdale Product Manager, Google App Engine On Tue, Jun 4, 2013 at 6:34 PM, Jason Galea ja...@lecstor.comjavascript: wrote: yeh, same here, but it looks like they should have said experimental Cloud Files API.. https://developers.google.com/appengine/docs/python/googlestorage/functions On Wed, Jun 5, 2013 at 11:27 AM, Bryce Cutt pand...@gmail.comjavascript: wrote: So, so I don't misunderstand, when you say experimental Files API you are not including this one? https://developers.google.com/appengine/docs/python/blobstore/blobstorefiles That is the one I thought was being deprecated when I saw the announcement. - Bryce On Tuesday, June 4, 2013 5:07:59 PM UTC-7, Max Ross wrote: Hi everyone, I'll try to batch answers to multiple questions into a single response. 1) We're not making any Blobstore announcements or decisions in this release. 2) The only thing we're announcing here is our intent to decommission the experimental Files API. That's https://developers.google.com/**appengine/docs/python/** googlestorage/functionshttps://developers.google.com/appengine/docs/python/googlestorage/functionsand https://developers.google.**com/appengine/docs/java/** googlestorage/overviewhttps://developers.google.com/appengine/docs/java/googlestorage/overview We'll give you fair warning before we actually turn it down. We're announcing this now to give everyone who uses the Files API enough time to move over to the Google Cloud Storage client library, which we're launching in Preview mode. 3) We (very quietly) announced the availability of the Google Cloud Storage client library in a posthttps://groups.google.com/forum/?fromgroups#!searchin/google-appengine/google$20cloud$20storage$20library/google-appengine/vXKiUHvPHRs/7ia8d_xO8KYJon this forum back in January. There are full-fledged docs for this library coming out with the official 1.8.1 announcement, including a guide to migrating off the Files API. I hope this helps. Thanks, Max On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote: +1 on this question I've been using blobstore for years, it's not so bad, it's bad but not too bad Should I invest my time and switch to Cloud Storage? (I don't even know how it works, whether it's practical for image like files etc. since blobstore did the job I've never investigated it) On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote: Regarding the Files API deprecation: Is this as of right now or as of the final release of SDK 1.8.1? I guess files already written will continue to work as is since they are no different than other blobstore files? Anything wrong with that assumption? With this announcement, Google's push for use of Cloud Storage, and the lack of a blobstore API in the PHP runtime should we be ready for you guys to announce the deprecation of the blobstore entirely? I hope not. I like the blobstore and how it is nicely and automatically isolated to a single app.
Re: [google-appengine] How do I create an App Engine application in the EU without a Premier account?
See: https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dDllb3FHLS1IdXVIcjVKR3FScklka1E6MQ I also updated my answer to the stackoverflow question you posted: http://stackoverflow.com/a/16890065/656408 Sorry for the confusion. On Tue, Jun 4, 2013 at 7:21 PM, Jon Ramvi jonbl...@gmail.com wrote: It's stated in the documentation that it's possible: If you have an App Engine Premier account, you can specify that your new application should reside in the European Union rather than the United States. For developers that do not have a Premier account, you will need to enable billing for applications that should reside in the European Union. https://developers.google.com/appengine/docs/python/gettingstartedpython27/uploading But you can't set up billing without creating the application first, and when the application is created you can't edit the location, so either isn't is possible for non-Premier accounts to create apps in the EU or I need a step by step guide on how to activate billing before creating the app. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- Johan Euphrosine (proppy) Developer Programs Engineer Google Developer Relations -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
The blobstore writing API has been experimental for years now. That being said, I wouldn't be surprised to see Google shut this one down soon too. Does GCS support fast concurrent writes the same way the blobstore writing API does? On Tuesday, June 4, 2013 7:20:49 PM UTC-7, Chris Ramsdale wrote: Jason, that is correct -- in a future release we are going to decommission the Experimental Google Cloud Storage API Functions. These APIs and their Experimental status are documented at the following links: - https://developers.google.com/appengine/docs/python/googlestorage/functions - https://developers.google.com/appengine/docs/java/googlestorage/overview Given this, we're moving the new Google Cloud Storage Client Libraryhttps://code.google.com/p/appengine-gcs-client/to Preview in the 1.8.1 release. Unlike Experimental features, Preview features are guaranteed to move to General Availability (GA). We encourage developers to start moving over to the new Cloud Storage Client Library as soon as possible. Information on getting started can be found at the open source project linked below. https://code.google.com/p/appengine-gcs-client/ Cheers, -- Chris Ramsdale Product Manager, Google App Engine On Tue, Jun 4, 2013 at 6:34 PM, Jason Galea ja...@lecstor.comjavascript: wrote: yeh, same here, but it looks like they should have said experimental Cloud Files API.. https://developers.google.com/appengine/docs/python/googlestorage/functions On Wed, Jun 5, 2013 at 11:27 AM, Bryce Cutt pand...@gmail.comjavascript: wrote: So, so I don't misunderstand, when you say experimental Files API you are not including this one? https://developers.google.com/appengine/docs/python/blobstore/blobstorefiles That is the one I thought was being deprecated when I saw the announcement. - Bryce On Tuesday, June 4, 2013 5:07:59 PM UTC-7, Max Ross wrote: Hi everyone, I'll try to batch answers to multiple questions into a single response. 1) We're not making any Blobstore announcements or decisions in this release. 2) The only thing we're announcing here is our intent to decommission the experimental Files API. That's https://developers.google.com/**appengine/docs/python/** googlestorage/functionshttps://developers.google.com/appengine/docs/python/googlestorage/functionsand https://developers.google.**com/appengine/docs/java/** googlestorage/overviewhttps://developers.google.com/appengine/docs/java/googlestorage/overview We'll give you fair warning before we actually turn it down. We're announcing this now to give everyone who uses the Files API enough time to move over to the Google Cloud Storage client library, which we're launching in Preview mode. 3) We (very quietly) announced the availability of the Google Cloud Storage client library in a posthttps://groups.google.com/forum/?fromgroups#!searchin/google-appengine/google$20cloud$20storage$20library/google-appengine/vXKiUHvPHRs/7ia8d_xO8KYJon this forum back in January. There are full-fledged docs for this library coming out with the official 1.8.1 announcement, including a guide to migrating off the Files API. I hope this helps. Thanks, Max On Tuesday, June 4, 2013 2:13:19 PM UTC-7, Kaan Soral wrote: +1 on this question I've been using blobstore for years, it's not so bad, it's bad but not too bad Should I invest my time and switch to Cloud Storage? (I don't even know how it works, whether it's practical for image like files etc. since blobstore did the job I've never investigated it) On Tuesday, June 4, 2013 11:45:35 PM UTC+3, Bryce Cutt wrote: Regarding the Files API deprecation: Is this as of right now or as of the final release of SDK 1.8.1? I guess files already written will continue to work as is since they are no different than other blobstore files? Anything wrong with that assumption? With this announcement, Google's push for use of Cloud Storage, and the lack of a blobstore API in the PHP runtime should we be ready for you guys to announce the deprecation of the blobstore entirely? I hope not. I like the blobstore and how it is nicely and automatically isolated to a single app. - Bryce On Tuesday, June 4, 2013 11:46:22 AM UTC-7, Richmond Manzana wrote: Hello Again Everyone! We've been busy since I/O! Pre-release SDKs for Python and Java here: http://code.google.com/p/**googl**eappengine/downloads/listhttp://code.google.com/p/googleappengine/downloads/list Please see the pre-release notes below. Cheers, Richmond Manzana App Engine Python SDK - Pre-Release Notes Version 1.8.1 ==**= - The Task Queue async API is now a GA feature. The asynchronous methods improve utilization by allowing your app to add, lease and delete multiple tasks in parallel. - Cloud Console projects are now created by default whenever a new App Engine app is created. This
[google-appengine] Re: Wordpress + AppEngine = PressEngine
Also, we'll be updating this blog on a fairly frequent basis until PHP goes GA: https://gaeforphp-blog.appspot.com/ There are already some tips related to WordPress there. And of course the blog itself runs on WordPress (btw, I believe the WordPress folks are quite particular about using a capital 'P'). cheers, Peter On Thursday, June 6, 2013 3:22:05 AM UTC+10, @Mlaynes wrote: more details about running Wordpress directly on GAE platform : https://developers.google.com/appengine/articles/wordpress best and happy coding.. @Mlaynes -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
But this means we will not be able to write programmatically to the blobstore anymore? We will be forced to use GCS instead of blobstore? — Sent from Mailbox for iPad On Wed, Jun 5, 2013 at 8:12 PM, Tom Kaitchuck tkaitch...@google.com wrote: Jon: The example you are pointing to is using two APIs. In java things under the package: com.google.appengine.api.blobstore are _not_ affected by this announcement. Things under the java package: com.google.appengine.api.files are affected by this announcement. We will be providing a migration guide for how to change code to use the Google Cloud Storage Client Libraryhttps://code.google.com/p/appengine-gcs-client/. This library is Preview as of 1.8.1 and as such is guaranteed to move to GA. Just to emphasize, this is a deprecation announcement, not a decommission. So your application will _not_ break with 1.8.1, but you should begin looking at how to port it to the new library. If you have questions about how to do this, feel free to create a thread on this group. On Wed, Jun 5, 2013 at 3:28 AM, jon jonni.g...@gmail.com wrote: Chris just to clarify, this is *not* being deprecated is it? https://developers.google.com/appengine/docs/java/blobstore/overview#Writing_Files_to_the_Blobstore I sure hope not because I'm using it heavily in my apps. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
