Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
hey Chris, et al.-- a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? -- Chris On Fri, Jun 7, 2013 at 6:00 PM, Chris ritterch...@gmail.com wrote: Jon, Any word on the timeline? - Chris -- 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.
The blobstore free daily quota :) — Sent from Mailbox for iPad On Sat, Jun 8, 2013 at 8:05 AM, Chris Ramsdale cramsd...@google.com wrote: hey Chris, et al.-- a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? -- Chris On Fri, Jun 7, 2013 at 6:00 PM, Chris ritterch...@gmail.com wrote: Jon, Any word on the timeline? - Chris -- 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.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
noted, and already looking into this. would you need the free quota spread across multiple buckets or would you be good with the free daily quota applied to a single bucket? -- Chris On Fri, Jun 7, 2013 at 11:29 PM, Stefano Ciccarelli sciccare...@gmail.comwrote: The blobstore free daily quota :) — Sent from Mailbox https://www.dropbox.com/mailbox for iPad On Sat, Jun 8, 2013 at 8:05 AM, Chris Ramsdale cramsd...@google.comwrote: hey Chris, et al.-- a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? -- Chris On Fri, Jun 7, 2013 at 6:00 PM, Chris ritterch...@gmail.com wrote: Jon, Any word on the timeline? - Chris -- 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. -- 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, That seems fair -- We're happy now. - Chris -- 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 free quota spread over multiple buckets would be better, but I think that a free quote applied to a single bucket could be fair. We can consider the actual blobstore as a single bucket. — Sent from Mailbox for iPad On Sat, Jun 8, 2013 at 8:42 AM, Chris Ramsdale cramsd...@google.com wrote: noted, and already looking into this. would you need the free quota spread across multiple buckets or would you be good with the free daily quota applied to a single bucket? -- Chris On Fri, Jun 7, 2013 at 11:29 PM, Stefano Ciccarelli sciccare...@gmail.comwrote: The blobstore free daily quota :) — Sent from Mailbox https://www.dropbox.com/mailbox for iPad On Sat, Jun 8, 2013 at 8:05 AM, Chris Ramsdale cramsd...@google.comwrote: hey Chris, et al.-- a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? -- Chris On Fri, Jun 7, 2013 at 6:00 PM, Chris ritterch...@gmail.com wrote: Jon, Any word on the timeline? - Chris -- 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. -- 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.
[google-appengine] Error: Server Error The server encountered an error and could not complete your request.
I really can't figured how to solve this error. every time i try to run my app i get the error Error: Server ErrorThe server encountered an error and could not complete your request. If the problem persists, please reporthttp://code.google.com/appengine/community.html your problem and mention this error message and the query that caused it. -- 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] I have old app without any data saved in datastore, can I change its datastire type to HRD directly without migrating it to another 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.
Re: [google-appengine] Error: Server Error The server encountered an error and could not complete your request.
Check the logs for your application at https://appengine.google.com/ The logs should give you some indication as to where the error is. On 8 June 2013 17:12, Peter Odhiambo pokay...@gmail.com wrote: I really can't figured how to solve this error. every time i try to run my app i get the error Error: Server ErrorThe server encountered an error and could not complete your request. If the problem persists, please reporthttp://code.google.com/appengine/community.html your problem and mention this error message and the query that caused it. -- 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] App Engine to Calendar Authentication
Hi James,
As pointed out by someone else earlier, the redirect URI needs to be https.
Also, if you are using Python, I've found the easiest method to implement
Oauth2 is to use the Oauth2Decorator supplied by Google.
See
https://developers.google.com/api-client-library/python/guide/google_app_engine#Decorators
It makes using Oauth a breeze! The example about halfway down the page
shows just how neat and simple it is. When I switched to using the
decorator, it saved me at least a page of code, and is more reliable and
results in neater code too.
Cheers,
Julie
On 6 June 2013 17:29, James Gralton james.gral...@ocado.com wrote:
Hi,
I am new to App Engine and am trying to write an application which will
access Google Calendar to get details of any events for the current time. I
am struggling to see how the authentication should work to permit access to
Calendar. I believe OAuth2 is the preferred authentication option so I have
a client_secrets.json file with the ClientID and Client Secret from an API
Access project I have separately created:
{
web:{
auth_uri:https://accounts.google.com/o/oauth2/auth;,
client_secret:xxx,
token_uri:https://accounts.google.com/o/oauth2/token;,
client_email:...@developer.gserviceaccount.com,
redirect_uris:[https://myapp.appspot.com/oauth2callback;],
client_x509_cert_url:
https://www.googleapis.com/robot/v1/metadata/x509/...@developer.gserviceaccount.com
,
client_id:123456789.apps.googleusercontent.com,
auth_provider_x509_cert_url:https://www.googleapis.com/oauth2/v1/certs;
,
javascript_origins:[https://myapp.appspot.com;]
}
}
This was a direct export from the API Access project using the 'Download
JSON' option. When I deploy my app engine application I get an error:
Error: redirect_uri_mismatch
The redirect URI in the request: http://myapp.appspot.com/oauth2callbackdid
not match a registered redirect URI
Learn more http://code.google.com/apis/accounts/docs/OAuth2.html
Request Details
scope=https://www.googleapis.com/auth/calendar
response_type=code
access_type=offline
redirect_uri=https://myapp.appspot.com/oauth2callback
display=page
client_id=123456789.apps.googleusercontent.com
It all looks fine to me so I am not sure what the error is telling me. Do
I need link the App Engine application to the API Access project in some
way. Am I missing something else fundamental.
If there is any additional information which will help you understand the
set up please let me know. I wanted to keep the post small.
Thanks
James
Notice: This email is confidential and may contain copyright material of
Ocado Limited (the Company). Opinions and views expressed in this message
may not necessarily reflect the opinions and views of the Company.
If you are not the intended recipient, please notify us immediately and
delete all copies of this message. Please note that it is your
responsibility to scan this message for viruses.
Company reg. no. 3875000.
Ocado Limited
Titan Court
3 Bishops Square
Hatfield Business Park
Hatfield
Herts
AL10 9NE
--
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: Deploy issues
Chris,
I can +1 this as well. I was experiencing occasional difficulties with
uploading my Go application this past week. The problem came and went; one
minute I was unable to upload my app, the next minute the very same upload
succeeded.
All's fine now though.
-
-Vinny P
Technology Media Advisor
Chicago, IL
My Go side project: http://invalidmail.com/
On Friday, June 7, 2013 4:33:35 PM UTC-5, Chris Ramsdale wrote:
hey Renzo / Tony--
there don't appear to be any systemic issues, but we're double checking
just in case. i'll post an follow-ups here.
-- Chris
Product Manager, Google App Engine
On Fri, Jun 7, 2013 at 12:56 PM, Tony França tonyl...@gmail.comjavascript:
wrote:
Having the same issue as Renzo with our Python app.
Actually sometimes the stack trace is different, besides the
BadStatusLine, we also get the stacktrace below.
I strongly believe this has nothing to do with my internet connection.
Google, any comments on this?
Thanks
Tony
Traceback (most recent call last):
File /home/qmagico/google_appengine/appcfg.py, line 171, in module
run_file(__file__, globals())
File /home/qmagico/google_appengine/appcfg.py, line 167, in run_file
execfile(script_path, globals_)
File /home/qmagico/google_appengine/google/appengine/tools/appcfg.py,
line 4507, in module
main(sys.argv)
File /home/qmagico/google_appengine/google/appengine/tools/appcfg.py,
line 4498, in main
result = AppCfgApp(argv).Run()
File /home/qmagico/google_appengine/google/appengine/tools/appcfg.py,
line 2686, in Run
self.action(self)
File /home/qmagico/google_appengine/google/appengine/
tools/appcfg.py, line 4233, in __call__
return method()
File /home/qmagico/google_appengine/google/appengine/tools/appcfg.py,
line 3244, in Update
updatecheck.CheckForUpdates()
File /home/qmagico/google_appengine/google/appengine/tools/appcfg.py,
line 629, in CheckForUpdates
runtime=self.config.runtime)
File
/home/qmagico/google_appengine/google/appengine/tools/appengine_rpc.py,
line 393, in Send
f = self.opener.open(req)
File /usr/lib/python2.7/urllib2.py, line 400, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.py, line 418, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.py, line 378, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.py, line 1215, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File
/home/qmagico/google_appengine/lib/fancy_urllib/fancy_urllib/__init__.py,
line 370, in do_open
req)
File /usr/lib/python2.7/urllib2.py, line 1180, in do_open
r = h.getresponse(buffering=True)
File /usr/lib/python2.7/httplib.py, line 1030, in getresponse
response.begin()
File /usr/lib/python2.7/httplib.py, line 407, in begin
version, status, reason = self._read_status()
File /usr/lib/python2.7/httplib.py, line 365, in _read_status
line = self.fp.readline()
File /usr/lib/python2.7/socket.py, line 447, in readline
data = self._sock.recv(self._rbufsize)
File /usr/lib/python2.7/ssl.py, line 241, in recv
return self.read(buflen)
File /usr/lib/python2.7/ssl.py, line 160, in read
return self._sslobj.read(len)
ssl.SSLError: The read operation timed out
On Friday, June 7, 2013 1:18:31 PM UTC-3, Renzo Nuccitelli wrote:
We were experiencing deploy issues yesterday. Here is the stack trace:
Traceback (most recent call last):
File
/home/qmagico/google_**appengine/google/appengine/**tools/appcfg.py, line
2284, in DoUpload
missing_files = self.Begin()
File
/home/qmagico/google_**appengine/google/appengine/**tools/appcfg.py, line
1947, in Begin
self.Send('/api/appversion/**create', payload=config_copy.ToYAML())
File
/home/qmagico/google_**appengine/google/appengine/**tools/appcfg.py, line
1892, in Send
return self.rpcserver.Send(url, payload=payload, **self.params)
File
/home/qmagico/google_**appengine/google/appengine/**tools/appengine_rpc.py,
line 393, in Send
f = self.opener.open(req)
File /usr/lib/python2.7/urllib2.**py, line 400, in open
response = self._open(req, data)
File /usr/lib/python2.7/urllib2.**py, line 418, in _open
'_open', req)
File /usr/lib/python2.7/urllib2.**py, line 378, in _call_chain
result = func(*args)
File /usr/lib/python2.7/urllib2.**py, line 1215, in https_open
return self.do_open(httplib.**HTTPSConnection, req)
File
/home/qmagico/google_**appengine/lib/fancy_urllib/**fancy_urllib/__init__.py,
line 370, in do_open
req)
File /usr/lib/python2.7/urllib2.**py, line 1180, in do_open
r = h.getresponse(buffering=True)
File /usr/lib/python2.7/httplib.**py, line 1030, in uygetresponse
response.begin()
File /usr/lib/python2.7/httplib.**py, line 407, in begin
version, status, reason = self._read_status()
File
[google-appengine] Re: Noobie: Sharing a collection of in-memory objects between instances.
On Thursday, June 6, 2013 4:27:59 AM UTC-5 wrote: My app is using a in-memory list that is accessed very often by font-end clients, my solution before was to use a static list. After gaining more info on GAE I know now that this wont be good because each instance would have it's own list (right?). It depends on how you architect your application. Written correctly, all instances can share a data list. On Thursday, June 6, 2013 4:27:59 AM UTC-5 wrote: So, are backends the best fit for that? There's nothing wrong with frontend instances for this job. Backends are more for long-running processes. Before anyone can give you a definitive answer, you need to give some more information about this problem. For instance, how many elements are in this list? What is the size of each element? How are you moving this list from the server to the client? How often does this list change? You said this list was static, so I assume this list won't be changing very often. In that case, you can use the memcache/datastore as Thiago suggested: Put each list element as an entity in the datastore, and set a cron to periodically pull a copy of the list and store it into memcache. Then your front end instances can pull the data from memcache/datastore. This way all your instances will share the same list. If this list is changing very rarely, what you can do is store it as a file in a Google Cloud Storage bucket, and configure the bucket as a website ( https://developers.google.com/storage/docs/website-configuration ). Whenever you need to change the list, your application on AppEngine can update the file: https://developers.google.com/storage/docs/xml-api-overview . You're also saving money this way since there's much less instance hours incurred. - -Vinny P Technology Media Advisor Chicago, IL My Go side project: http://invalidmail.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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: App Engine to Calendar Authentication
On Thursday, June 6, 2013 2:29:32 AM UTC-5, James Gralton wrote: This was a direct export from the API Access project using the 'Download JSON' option. When I deploy my app engine application I get an error: Error: redirect_uri_mismatch The redirect URI in the request: http://myapp.appspot.com/oauth2callback did not match a registered redirect URI client_id=123456789.apps.googleusercontent.com It all looks fine to me so I am not sure what the error is telling me. Do I need link the App Engine application to the API Access project in some way. Am I missing something else fundamental. Hello James, Did you whitelist the redirect URI when you created your application? I created an imgur album to show the steps: http://imgur.com/a/UUXyI . On the second screen to creating your client application, there is a list of URLs that are authorized for redirects; the Authorized Redirect URIs part of the screen. You need to put any URI that is allowed to receive redirects/callbacks into that text box. Also make sure your redirect URI is https, as Julie suggested. - -Vinny P Technology Media Advisor Chicago, IL My Go side project: http://invalidmail.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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: 1.8.1 Pre-release SDKs Available.
On Saturday, June 8, 2013 2:04:23 AM UTC-4, Chris Ramsdale wrote: what would keep you from migrating over to a Cloud Storage-based solution? 1. Its a bit of a pain to get set up with cloud storage, especially all the service name account and permissions stuff. Blobstore is nice because it just works. 2. I have mobile clients which use the blobstore upload system. I would want the existing clients to continue to work if I migrated to cloud storage. I looked into the cloud storage API and you couldn't exactly mimic the blobstore protocol. 3. Blobstore doesn't require unique filenames. so when uploading files, I hardcode in a file name since it doesn't matter. To switch to cloud storage, I'd have to come up with a unique filename. --Alex -- 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.
Hi Chris, thanks for stopping by. *My need: Better libraries.* What I liked about the Files API (and particularly in regards to the Blobstore) is that it made writing files so unbelievably easy. For example, in Java all I needed to do was get an instance of FileService, then I could write and read using openWriteChannel/openReadChannel. The Files API handled the dirty part of configuring access to the datastore, managing the write, etc. Frankly, I think the Files API is one of the best engineered parts of GAE* (give whoever wrote that API a raise and a promotion please!). * But you look at the javadoc for the Java Cloud Storage library, and it's an utter mess. See for yourself: https://developers.google.com/resources/api-libraries/documentation/storage/v1beta2/java/latest/ . For one, there's not enough examples. Two, I have to mess around with BucketAccessControls and Builders and a whole mess of things. Chris, I just want to write some files to persistent storage, I don't want to have to micromanage everything else and deal with extra fluff. I'll micromanage if I have to, but the Blobstore took care of that for me. Get the guy who wrote the Files API and put him to work on writing the GCS library. - -Vinny P Technology Media Advisor Chicago, IL My Go side project: http://invalidmail.com/ On Saturday, June 8, 2013 1:04:23 AM UTC-5, Chris Ramsdale wrote: a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? -- Chris -- 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.
On Fri, Jun 7, 2013 at 11:04 PM, Chris Ramsdale cramsd...@google.comwrote: hey Chris, et al.-- a bunch of great feedback that we'll continue to address. in regards to timeline, we have no plans of decommissioning this API before end of year. that said, assuming the following: - App Engine = Google Cloud Storage performance is equivalent to (if not better than) App Engine = Blobstore - all blobs were auto-migrated over to Cloud Storage (free of charge) - all existing URLs just worked what would keep you from migrating over to a Cloud Storage-based solution? Some questions: * Will the current upload mechanism be preserved? Looking through the docs it appears the answer is that you create a signed url directly into GCS and have the client POST/PUT it, which seems like it should be compatible with the existing BlobstoreService.getUploadUrl() approach. But how do we get notification when the upload is complete? Right now the blobstore upload mechanism gives us a callback, and I do important things on this callback. * Will this work with the image service the way the blobstore does now? I transform, resize, and crop images on the fly - this rarely-lauded feature is actually one of my favorite parts of GAE. * Will existing blobstore-based image urls be preserved? I have a lot of these in my datastore. * What does the GAE dev environment do with the GCS apis? What about the Local Unit Testing framework? As long as there are sane answers to these questions, I have no objection to GCS... although it will require that I rewrite and some code: * I read PDF data out of the blobstore using the files api, send it off to a service for transformation into an image, then write the image back to the blobstore. This sounds pretty straightforward with GCS. * I de-dup all uploaded images using the hash, and track image references. This means I have a lot of data referencing BlobKeys in the datastore. This brings up the question, if data is migrated from Blobstore to GCS, what are the new keys? Will it be clear how to migrate this data? I don't object to rewriting code as long as the migration path is clear. I can appreciate consolidating development effort around a single blobstore-ish offering. Thanks, Jeff -- 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: server side vs client side
On Thursday, June 6, 2013 3:06:58 PM UTC-5, LC wrote: Well, my question is quite general... So, I want to write a web app that every time the user clicks on a button it connects to 5 or 6 other websites, reads 2 or 3 pages from each one, does some processing on the data read from these sites and then show some result to the user. At first I thought to create a jsp do to the job, but then I thought that maybe doing everything (the connection to the websites and data processing) on the client side using javascript would save me a lot of server side resources (and money) Depends on what you're processing. If these other sites are sending back JSONP/AJAX ( http://en.wikipedia.org/wiki/Ajax_(programming) ) responses, then you can process it in Javascript on the client side. It's quite easy to do (there are a bunch of AJAX tutorials on the web) and relatively fast since you're using the user's computer to do the processing and data retrievals. However, if the sites you're reading from are serving regular web pages (not JSONP responses) then you have to use server side code. The reason is that Javascript code is sandboxed; it's not allowed to pull just any arbitrary document on the web. You'll need to write a scraper ( http://en.wikipedia.org/wiki/Web_scraping) to urlfetch the sites and process the HTML. Fortunately there are libraries for this: BeautifulSoup ( http://www.crummy.com/software/BeautifulSoup/ ) for Python and HTMLUnit ( http://htmlunit.sourceforge.net/ ) for Java. - -Vinny P Technology Media Advisor Chicago, IL My Go side project: http://invalidmail.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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Huge increase in datastore reads - hit $1,000 a day
The more I think about this, the more I think the fundamental problem is the aggressive retry schedule on the task queue. This is really easy to fix in your own app. With the exception of the task queue, it seems like every GAE expense grows proportionally with user traffic. However, one coding error can easily cause the task queue to DOS your app with retries. For most tasks, if two tries don't work then you might as well wait an hour before trying again - chances are some third-party service is down or there may be a code issue that requires developer intervention. Maybe you catch the problem after a couple hours, so your bill is 4X what it normally would be... but this is better than the two alternatives: 100X bill, or your app going down due to quota exhaustion. I'm going to change my retry schedule now, and I recommend everyone else do the same. Jeff On Fri, Jun 7, 2013 at 5:32 AM, Marcel Manz marcel.m...@gmail.com wrote: I guess open an issue for these suggestions and star them would be a very good way for GAE Team to hear us. Added, please star: https://code.google.com/p/googleappengine/issues/detail?id=9455 Marcel -- 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.
[google-appengine] Re: Why is only one of my instances taking all the traffic?
Hello Andrew, Here's a App Engine Groups discussion that is very similar to your question (I posted a detailed and cited comment in the replies): https://groups.google.com/forum/?fromgroups#!topic/google-appengine/5KRMpQ-9UQc The short version is, what you're seeing is intended behavior. The idle (also called resident) instance is there to buffer incoming requests; the dynamic instance is launched and run to handle standard traffic. - -Vinny P Technology Media Advisor Chicago, IL My Go side project: http://invalidmail.com/ On Thursday, June 6, 2013 2:39:21 PM UTC-5, Andrew Brogdon wrote: I've got a small App Engine site built in Java, and I don't understand the traffic splitting behavior that's going on. I have it set to maintain one idle instance and spin up others as is sees fit. This, however, is what I see in the Instances section of the dashboard: *QPSLatency Requests Errors Age * 0.000 0.0 ms100 1 day, 1:56:27 (Idle) 0.083 162.0 ms 541 0 4:03:04 (Dynamic) My idle instance is somehow dodging work, while the dynamic one is handling almost all the requests. Why is this happening? If I'm only going to be making use of one instance, I'd prefer to avoid having two, for obvious reasons. -Andrew -- 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] [Java] PutException: Failed to complete in the allocated time 4492ms
Hi, I just found this error in my logs: java.util.concurrent.ExecutionException: com.google.appengine.api.search.PutException: Failed to complete in the allocated time 4492ms at com.google.appengine.api.utils.FutureWrapper.setExceptionResult(FutureWrapper.java:63) at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94) I would love to know how to increase this timeout. Didn't find it so far ... Regards Stephan -- 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.
I will migrate to GCS if: * All conditions stated by Chris Ramsdale are met * It is fully compatible with Blobstore's dynamic resize feature (eg the =s parameter still works) * It allows for a file upload (especially from mobile apps) to be completed in one HTTP request * It sets far future expiry header +1 to everything Jeff said. -- 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.
