[google-appengine] Re: Google App Engine SDK 1.8.0 is now available!

[Shay Erlichmen]

BTW the link to the dmg file for the mac is wrong, its pointing 
to http://googleappengine.googlecode.com/files/oogleAppEngineLauncher-1.8.0.dmg 
instead of http://googleappengine.googlecode.com/files/*G*
oogleAppEngineLauncher-1.8.0.dmg

On Thursday, May 9, 2013 2:36:21 AM UTC+3, Richmond Manzana wrote:
>
> Hi everyone,
>
> We're happy to announce that we have released the 1.8.0 SDK.
>
>
> For more details, please read our blog post and release notes.
>
> Release notes for Python:
> http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes
>
> Release notes for Java:
> http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes
>
> Release notes for Go:
> https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes
>
> Cheers!
>
> P.S. If you don't see the appengine-maven-plugin release, it takes a while 
> to replicate.  You can either wait a little bit, or if you add the 
> following in the pom you can see the master:
>
>  
>
>sonatype-google-releases
>Sonatype Google Releases
>
> https://oss.sonatype.org/service/local/repositories/google-releases/content
> 
>
>
>
> Richmond Manzana
> Technical Program Manager
> Google 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 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: Google App Engine SDK 1.8.0 is now available!

[Shay Erlichmen]

This is a very SMALL change for jumping from 1.7.7 to 1.8, what are you 
hiding? :) 

On Thursday, May 9, 2013 2:36:21 AM UTC+3, Richmond Manzana wrote:
>
> Hi everyone,
>
> We're happy to announce that we have released the 1.8.0 SDK.
>
>
> For more details, please read our blog post and release notes.
>
> Release notes for Python:
> http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes
>
> Release notes for Java:
> http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes
>
> Release notes for Go:
> https://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes
>
> Cheers!
>
> P.S. If you don't see the appengine-maven-plugin release, it takes a while 
> to replicate.  You can either wait a little bit, or if you add the 
> following in the pom you can see the master:
>
>  
>
>sonatype-google-releases
>Sonatype Google Releases
>
> https://oss.sonatype.org/service/local/repositories/google-releases/content
> 
>
>
>
> Richmond Manzana
> Technical Program Manager
> Google 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 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: Important for Python developers - Updates to the Development Server in 1.7.6

[Shay Erlichmen]

I also notice that now I need to choose between debug and live code update 
(AKA hot patching).
Debugging while code editing was one of killers features of the old server, 
please find a solution for this also.

On Thursday, March 21, 2013 10:02:19 AM UTC+2, Shay Erlichmen wrote:
>
> Thanks for the info Andrew, I figure that startup script was the way to go 
> but wasn't sure on how.
> I think that you need to figure how to release a version that wouldn't 
> required manual wireup for debugging on at least make it very easy to do.
>
> On Thursday, March 21, 2013 6:50:20 AM UTC+2, Andrew Jessup wrote:
>>
>> Hi Shay,
>>
>> A key goal of the new development server was to provide a runtime 
>> environment closer to how your apps actually run in production, which is 
>> why a single app will now often run in multiple processes. This raises an 
>> interesting debugging challenge - how do we easily bind the right process a 
>> debugger to, particularly if that process hasn't started yet? How do we 
>> prevent that process from being automatically restarted should you change 
>> the file?
>>
>> In our open source mirror project for the new dev_appserver we've added 
>> some additional flags that allow you to more tightly control process 
>> execution and provide hooks that allow you to write scripts to control how 
>> and where to attach a debugger. We hope to tighten this API and include 
>> with dev_appserver it in the next release of the App Engine SDK. 
>>
>> If you'd like to take a look now, I would point you to this discussion 
>> https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28and
>>  in particular the document linked there that summarizes our proposed 
>> debugging approach and provides some sample code to get started.
>>
>>
>>
>>
>> On Thu, Mar 21, 2013 at 1:27 AM, Shay Erlichmen wrote:
>>
>>> I worked with preview version of it and I was too embarrassed to ask, 
>>> but now that this is official quick question:
>>> How do you debug code now? in the old dev server (under eclipse + pydev) 
>>> all I have todo is set a breakpoint it seem now that this is no longer 
>>> working (latest pydev + juno).
>>> I imagine that I can attach to the process but please tell me that this 
>>> is not the optimal way. 
>>>
>>>
>>> On Wednesday, March 20, 2013 2:57:02 AM UTC+2, Andrew Jessup wrote:
>>>>
>>>> In the 1.7.6 release of App Engine we’ve included a major upgrade to 
>>>> the Development Server in the Python SDK, designed to make development 
>>>> faster and more faithfully reproduce the production App Engine runtime 
>>>> environment. The new version more faithfully simulates elements of the 
>>>> production App Engine environment, such as concurrent requests and 
>>>> backends, and in most cases this will also mean your apps run faster. We 
>>>> previously included this in the 1.7.5 release as dev_appserver2.py, in 
>>>> this 
>>>> release it has become the default dev_appserver.py
>>>>
>>>> While we're confident the improvements are substantial, as with any 
>>>> major change, some things work a little differently with the new 
>>>> dev_appserver. Here’s a few changes to watch out for:
>>>>
>>>>- Your local development admin console will run on it’s own server 
>>>>and port, rather than under /_ah/admin
>>>>- We’ve changed the defaults for new applications, such as using 
>>>>HRD rather than Master/Slave, and using SQLlite to emulate the 
>>>> datastore.
>>>>- We’ve cleaned up many command line flags and arguments
>>>>- Python 2.5 applications are no longer officially supported on the 
>>>>new Development Server in line with our deprecation announcement 
>>>> (**although 
>>>>they may still be run)
>>>>
>>>> We’ve provided a detailed summary of all the changes to the Development 
>>>> Server in our 
>>>> documentation<https://developers.google.com/appengine/docs/python/tools/old_devserver>.
>>>>  
>>>>
>>>>
>>>> The the legacy dev_appserver.py remains available in the Python SDK as 
>>>> old_dev_appserver.py for those who still require it. However if you 
>>>> encounter any issues with the new Development Server we strongly encourage 
>>>> you to report them on our issue 
>&

[google-appengine] Re: 1.7.6 Speedy Deploy

[Shay Erlichmen]

unsung heroes! 
Feel free to mention this sort of updates in the release notes I'm sure no 
one is going to complain.

On Wednesday, March 20, 2013 7:09:51 PM UTC+2, Randy Shoup wrote:
>
> Thanks for noticing!  We've been hard at work on lots of improvements, 
> with particular emphasis on deployment latencies.  We are far from done, 
> though, so please stay tuned ...
>
> Randy Shoup
> Director, Google App Engine
>
> On Wednesday, March 20, 2013 7:30:44 AM UTC-7, Shay Erlichmen wrote:
>>
>> It seems that with the new release this morning upload are VERY fast, 
>> 60-70 seconds deploy takes now 10-12 seconds. 
>> I hope it will stay this way.
>>
>

-- 
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: Important for Python developers - Updates to the Development Server in 1.7.6

[Shay Erlichmen]

Thanks for the info Andrew, I figure that startup script was the way to go 
but wasn't sure on how.
I think that you need to figure how to release a version that wouldn't 
required manual wireup for debugging on at least make it very easy to do.

On Thursday, March 21, 2013 6:50:20 AM UTC+2, Andrew Jessup wrote:
>
> Hi Shay,
>
> A key goal of the new development server was to provide a runtime 
> environment closer to how your apps actually run in production, which is 
> why a single app will now often run in multiple processes. This raises an 
> interesting debugging challenge - how do we easily bind the right process a 
> debugger to, particularly if that process hasn't started yet? How do we 
> prevent that process from being automatically restarted should you change 
> the file?
>
> In our open source mirror project for the new dev_appserver we've added 
> some additional flags that allow you to more tightly control process 
> execution and provide hooks that allow you to write scripts to control how 
> and where to attach a debugger. We hope to tighten this API and include 
> with dev_appserver it in the next release of the App Engine SDK. 
>
> If you'd like to take a look now, I would point you to this discussion 
> https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28and
>  in particular the document linked there that summarizes our proposed 
> debugging approach and provides some sample code to get started.
>
>
>
>
> On Thu, Mar 21, 2013 at 1:27 AM, Shay Erlichmen 
> 
> > wrote:
>
>> I worked with preview version of it and I was too embarrassed to ask, but 
>> now that this is official quick question:
>> How do you debug code now? in the old dev server (under eclipse + pydev) 
>> all I have todo is set a breakpoint it seem now that this is no longer 
>> working (latest pydev + juno).
>> I imagine that I can attach to the process but please tell me that this 
>> is not the optimal way. 
>>
>>
>> On Wednesday, March 20, 2013 2:57:02 AM UTC+2, Andrew Jessup wrote:
>>>
>>> In the 1.7.6 release of App Engine we’ve included a major upgrade to the 
>>> Development Server in the Python SDK, designed to make development faster 
>>> and more faithfully reproduce the production App Engine runtime 
>>> environment. The new version more faithfully simulates elements of the 
>>> production App Engine environment, such as concurrent requests and 
>>> backends, and in most cases this will also mean your apps run faster. We 
>>> previously included this in the 1.7.5 release as dev_appserver2.py, in this 
>>> release it has become the default dev_appserver.py
>>>
>>> While we're confident the improvements are substantial, as with any 
>>> major change, some things work a little differently with the new 
>>> dev_appserver. Here’s a few changes to watch out for:
>>>
>>>- Your local development admin console will run on it’s own server 
>>>and port, rather than under /_ah/admin
>>>- We’ve changed the defaults for new applications, such as using HRD 
>>>rather than Master/Slave, and using SQLlite to emulate the datastore.
>>>- We’ve cleaned up many command line flags and arguments
>>>- Python 2.5 applications are no longer officially supported on the 
>>>new Development Server in line with our deprecation announcement 
>>> (**although 
>>>they may still be run)
>>>
>>> We’ve provided a detailed summary of all the changes to the Development 
>>> Server in our 
>>> documentation<https://developers.google.com/appengine/docs/python/tools/old_devserver>.
>>>  
>>>
>>>
>>> The the legacy dev_appserver.py remains available in the Python SDK as 
>>> old_dev_appserver.py for those who still require it. However if you 
>>> encounter any issues with the new Development Server we strongly encourage 
>>> you to report them on our issue 
>>> tracker<https://code.google.com/p/googleappengine/issues/list>
>>> .
>>>
>>> We hope you like the new changes, and that you enjoy snappier app 
>>> development with fewer surprises on deployment. Keep on coding!
>>>
>>> - Andrew Jessup, for the App Engine team
>>
>>  -- 
>> 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 .
>> To post to this group, send emai

[google-appengine] 1.7.6 Speedy Deploy

[Shay Erlichmen]

It seems that with the new release this morning upload are VERY fast, 60-70 
seconds deploy takes now 10-12 seconds. 
I hope it will stay this way.

-- 
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: Important for Python developers - Updates to the Development Server in 1.7.6

[Shay Erlichmen]

I worked with preview version of it and I was too embarrassed to ask, but 
now that this is official quick question:
How do you debug code now? in the old dev server (under eclipse + pydev) 
all I have todo is set a breakpoint it seem now that this is no longer 
working (latest pydev + juno).
I imagine that I can attach to the process but please tell me that this is 
not the optimal way. 

On Wednesday, March 20, 2013 2:57:02 AM UTC+2, Andrew Jessup wrote:
>
> In the 1.7.6 release of App Engine we’ve included a major upgrade to the 
> Development Server in the Python SDK, designed to make development faster 
> and more faithfully reproduce the production App Engine runtime 
> environment. The new version more faithfully simulates elements of the 
> production App Engine environment, such as concurrent requests and 
> backends, and in most cases this will also mean your apps run faster. We 
> previously included this in the 1.7.5 release as dev_appserver2.py, in this 
> release it has become the default dev_appserver.py
>
> While we're confident the improvements are substantial, as with any major 
> change, some things work a little differently with the new dev_appserver. 
> Here’s a few changes to watch out for:
>
>- Your local development admin console will run on it’s own server and 
>port, rather than under /_ah/admin
>- We’ve changed the defaults for new applications, such as using HRD 
>rather than Master/Slave, and using SQLlite to emulate the datastore.
>- We’ve cleaned up many command line flags and arguments
>- Python 2.5 applications are no longer officially supported on the 
>new Development Server in line with our deprecation announcement (although 
>they may still be run)
>
> We’ve provided a detailed summary of all the changes to the Development 
> Server in our 
> documentation.
>  
>
>
> The the legacy dev_appserver.py remains available in the Python SDK as 
> old_dev_appserver.py for those who still require it. However if you 
> encounter any issues with the new Development Server we strongly encourage 
> you to report them on our issue 
> tracker
> .
>
> We hope you like the new changes, and that you enjoy snappier app 
> development with fewer surprises on deployment. Keep on coding!
>
> - Andrew Jessup, for the App Engine team

-- 
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: import errors with sdk 1.5.3

[Shay Erlichmen]

open issue 
5737

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/d8I2AX4q1NIJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Has GAE Changed The Way They Handle Emails?

[Shay Erlichmen]

2000 emails is not a factor for spammer who send mails by 500K to 1M mails a 
day.
2000 emails is a factor for a free non profit app 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Has GAE Changed The Way They Handle Emails?

[Shay Erlichmen]

Yes as of 1.5 only domain managed by Google (Gmail or Google Apps) can send 
emails using GAE.
They also reduce the free quote of emails from 2000 to 100 (for new 
apps) claiming that it for "reliably" which is total BS.
It is OK to want to make more money from your platform but at least don't 
treat us (customers) like total morons.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: app dashboard not accessible

[Shay Erlichmen]

Same here

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Uploading to the blobstore directly

[Shay Erlichmen]

I spend several hours searching for something like your code and could
find any.
This code is kinda what I wrote myself (Yours is better).

The thing is I that really think that there should be a static/fixed
endpoint for uploads.

The flow should be something like:
1. You upload/post to a fixed (configurable) url i.e. /upload/?
param1=val¶m2=val
2. That url is not limited to the 1MB and it will store the content in
the blobstore
3. You will define using regex which dispatcher/controller will
receive the upload results
4. This dispatcher/controller will be called using a forward redirect
and not an actual redirect
5. The dispatcher/controller will return a response which doesn't have
to be a redirect

--- 10 minutes pause ---
OK, I open an issue for it 
http://code.google.com/p/googleappengine/issues/detail?id=3686

On Sep 6, 10:21 pm, John McLaughlin 
wrote:
> I think you've got the picture.  I was dealing with this sort of thing
> a couple weeks ago and wrote a cookbook page that kinda-sorta makes it
> a one step 
> process.http://appengine-cookbook.appspot.com/recipe/just-in-time-blobstore-u...
>
> Let me know if it's helpful.
>
> -- John
>
> On Sep 5, 11:03 am, Shay Erlichmen  wrote:
>
>
>
>
>
>
>
> > I have an OCR service* that allows you to upload pictures and get the
> > text.
> > The service has a very simple REST API (/post_image) where you POST
> > the image (and some metadata) and you get the result in JSON format.
> > The service is called from Flash, Web, and other clients.
>
> > So far I've used blobs in the datastore to store and serve the images
> > and I want to move to the blobstore (in order to use get_serving_url)
> > As far as I can see, I need to break my /post_image method into two
> > steps: the first step will be to call a new method /prepare_upload
> > which will get me the upload url (by calling create_upload_url(...)),
> > then call the returned upload_url and get the JSON data.
> > To make things more awkward, the result from the upload url cannot be
> > the JSON data itself but a redirect to a url that returns the JSON
> > data.
>
> > Questions:
> > 1. Did I analyze it right? Is is a two stepper flow for my clients?
> > are there any unnecessary steps??.
> > 2. In case I got it correct, are there any plans for direct upload to
> > the blobstore (without calling create_upload_url(...))
>
> > * service for illustration purpose only, I don't really have this
> > exact service.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Uploading to the blobstore directly

[Shay Erlichmen]

Your steps seem logical but,
Problem is that the some clients are necessary in the browser, so
there is no form to submit.
Those clients needs a "fixed" end point to upload the data (or call a
"fixed" end point that will return the upload url"

On Sep 7, 6:29 pm, timwhunt  wrote:
> I think I have this right, so hopefully to clarify:
>
> 1) You get the upload URL for an HTML form for your user to upload the
> image.  Part of forming that uploading URL is to identify the handler
> code (e.g., Servlet in Java)
> 2) Your handler code gets called by the Blobstore after the upload is
> complete and that handler can work with the uploaded data and you'll
> work with the the key for the blob
> 3) Your handler sends a redirect command back to the user's browser
> directing them to the page they need to go to for status/results.
> That redirect URL generally includes a parameter identifying which
> blob upload (it's key) you're dealing with.
> 4) The user's browser is redirected to that page, where your code uses
> the blobstore key (from the URL parameter) to process and in your case
> return the OCR data.
>
> So from the client point of view, they submit a forum with a file
> upload part, and they get redirected to the page that provides the
> results.
>
> Someone please correct if necessary.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Uploading to the blobstore directly

[Shay Erlichmen]

I have an OCR service* that allows you to upload pictures and get the
text.
The service has a very simple REST API (/post_image) where you POST
the image (and some metadata) and you get the result in JSON format.
The service is called from Flash, Web, and other clients.

So far I've used blobs in the datastore to store and serve the images
and I want to move to the blobstore (in order to use get_serving_url)
As far as I can see, I need to break my /post_image method into two
steps: the first step will be to call a new method /prepare_upload
which will get me the upload url (by calling create_upload_url(...)),
then call the returned upload_url and get the JSON data.
To make things more awkward, the result from the upload url cannot be
the JSON data itself but a redirect to a url that returns the JSON
data.

Questions:
1. Did I analyze it right? Is is a two stepper flow for my clients?
are there any unnecessary steps??.
2. In case I got it correct, are there any plans for direct upload to
the blobstore (without calling create_upload_url(...))





* service for illustration purpose only, I don't really have this
exact service.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.