Excelent news! Specially to protect applications from cold start.
How can I configure WarmUp requests and Always On using Java?
Thanks and congratulations!
On Nov 18, 8:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get
I love App Engine, it gets better and better with every release and
let's you do more and more cool stuff.
I'm really looking forward to it going live.
- Alexander
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, s
That’s a fantastic release. Can’t wait to have it in production.
Great job App Engine Team.
Tim
--
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 thi
Metadata Queries - what's this?
--
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
For GAE/J you can reference this project:
http://code.google.com/p/dance-dance-robot/
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine
On Thu, Nov 18, 2010 at
Hi Ikai,
What about the OpenId SSL support? Is it part of this release ?
Regards,
Alexandre Vivien
On 18 nov, 17:27, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.
Is the high performance image serving from the blobstore through
getServingUrl / get_serving_url still going to be limited to 1600x1600?
I could really use 1920x1080 (which actually is fewer pixels).
--
You received this message because you are subscribed to the Google Groups
"Google App Engine"
Is there an easy way to get this to work in Eclipse? Thanks!
On Nov 18, 3:17 pm, "Ikai Lan (Google)"
wrote:
> Always On will be a paid feature you enable in the admin console.
>
> I'll post some light sample code for channel API and warmup requests in a
> bit.
>
> --
> Ikai Lan
> Developer Progra
Really looking forward to this release. This will make a big
difference for my company's apps.
Thanks Googlers!
--
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 unsub
Since I'm too excited to wait, I opened the new appengine-web.xsd in
1.4.0-pre to see how to configure the new features. There is a new
tag with a boolean value. Of course I tried
it but it gives me an error:
400 Bad Request
Error when loading application configuration:
Value 'warmup' for key ???
always on is *huge*
that, combined with the generally improved latency of datastore
queries of late extinguishes my feelings that perhaps I had made the
wrong choice to run our website on GAE
On Nov 18, 10:41 pm, 风笑雪 wrote:
> It's an amazing release, waiting for the docs.
> --
> keakon
>
Sergio,
The prerelease SDKs are for the development server only; the
production servers won't support the features until the actual
release. You can't deploy with the new features enabled, and should
continue to use the current SDK for deployed applications.
On Nov 18, 9:47 pm, Sergio Lopes wro
A great release!
thanks,
-g.
On Nov 19, 12:27 am, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
> ...
> As usual, we value your feedback, so don't hesitate to evaluate these SDKs
> and le
Wow a lot of work packed there, congrats App Engine team!
I'm surprised about the new 10 minutes deadline on Cron and Task
Queues. A short while back you were explaining that long-running
requests are bad for the App Engine ecosystem. Is it not the case for
Task Queues or are you just confident th
Looking forward to always on feature which I will use immediately (and
pay for).
Please let me know when I can beta test or buy it.
DROID ( rodsit[at]gmail.com )
On Nov 18, 11:17 pm, "Ikai Lan (Google)"
wrote:
> Always On will be a paid feature you enable in the admin console.
>
> I'll post some
Cool !
Has anybody figured out how to use the Channel Api and where to find
the JS files to do the clientside longpolling, iframe or whatever
comet stuff ?
I remember having played with the dance robot long time ago, that was
cool, but there there was a huge bloat load of Javascript (the whole
cl
Wow, this great stuff, definitely looking forward to the channel api:)
Great job App Engine team!
On Nov 18, 5:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.
I must say this release makes gae better than ec2!
On Nov 19, 6:27 am, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.com/p/googleappengine/downloads/list
>
> We're s
Really amazing.
Can't wait to see it release officially.
--
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
Looks like a huge release, can't wait to check it out. Congrats and
thanks Google!
On Nov 18, 2:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.com/p/googleappe
SSL support for OpenID should be live now. There was an issue which
prevented it from being released at the same time as the 1.3.8 release
but that issue has since been fixed.
--Matthew
On Nov 18, 4:38 pm, Alexandre Vivien wrote:
> Hi Ikai,
>
> What about the OpenId SSL support? Is it part of th
Hey does this mean that we can finally deploy grails apps and not get
errors because its having to start up?
--
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 unsubscr
+1 this is amazing. We're partying over here, just seeing this:
quite literally, we were just about to rewrite code around the
1MB limit, timeouts, django, and more.
thank you thank you thank you,
adam
--
You received this message because you are subscribed to the Google Groups
"Google A
sounds good. I was feeling torn between grails and pure python. On the
one hand grails gives you so much but ont he other hand its not cloud
friendly it seems. I was on the verge of having to goto EC2 for a new
app, if this works out I wont need to :)
--
You received this message because you are
Fantastic release! Great work guys!!
On Nov 18, 11:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.com/p/googleappengine/downloads/list
>
> We're still working
WOW! Let me say that again, WOW! This month has been totally exciting
and full of pleasant surprises. And this seems to be going towards
being one of the best release ever!
Great work guys, keep it up.
-Nischal
On Nov 19, 12:14 pm, Benjamin wrote:
> Really amazing.
> Can't wait to see it releas
Hi
- The deadline for Task Queue and Cron requests has been raised to 10
minutes.
Do you mean that now each Task Queue and Cron request can run for 10
min, instead of the old 30 seconds limit??!
Jagan
On Nov 19, 3:27 am, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let every
Hi,
I'm experience issues with the 1 Mb URL fetch limitation when I post
files with ResumableUpload against Google Docs (Resumable Upload is
using the URLfetch functionality in the lower layers). I'm a bit
confused though regarding the reqeust limit (1Mb) and response-limit
(32 Mb) in the 1.4.0 SD
Great work, guys!
Really afraid to see a horrible uninformed anti-GAE post now #1 on
Hacker News http://www.carlosble.com/?p=719
I can't believe my eyes.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to g
Just to be clear, is the deadline for starting up a new instance,
including from the warmup web hook, still at 30 seconds? Or is it 10
minutes as for the tasks and cron apis? One of the issues with cold
starts was to get heavier frameworks (Spring, Grails) up before the 30
seconds deadline.
--
Yo
Fantastic release!
I wanted a clarification about URLFetch.
With a response size limit increased up to 32mb I also would expect a
new max deadline that seems not changed (10 seconds)
Thanks!
On Nov 18, 11:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know th
Instance startup is still 30 seconds.
I honestly think you need to rethink your platform stack if you can't
get you average startup
time (on a good day ;-) to less than 10 - 15sec.
Rgds
T
On Nov 23, 1:12 am, Starman wrote:
> Just to be clear, is the deadline for starting up a new instance,
> i
> The deadline for Task Queue and Cron requests has been raised to 10 minutes.
This is great! They're still counting towards the CPU seconds limit,
right?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to
Ikai,
Now that the Channels API is open to everyone, do you know when we
might see some documentation for it? Just the javadocs would do for
now.
Thanks,
CV
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email
Why was the decision made to make this an app-wide one time only nuke
button?
I think enabling/disabling it in app.yaml per-upload would be much
more useful.
On Nov 23, 8:30 pm, "Ikai Lan (Google)"
wrote:
> You'll be able to download code, but anyone that wants to turn it off will
> be able to g
Sorry if I missed it, but are the regular requests (not queues/cron)
still limited to 30 seconds?
On Nov 18, 2:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
> I just wanted to let everyone know that prerelease SDK 1.4.0 is out! Get it
> from the Google Code project:
>
> http://code.google.c
If the guy uploading enables downloads to be malicious, he could
equally just post up the code somewhere.
That being said, I hadn't thought about the case of accidentally re-
enabling and then having the account compromised. Even still, not
being able to ever turn it back on seems short sighted. P
Icai, I was for an opt-in solution but IMHO One way disable button is
also OK and also it takes into account the interests of newbies.
On Nov 24, 10:51 pm, "Ikai Lan (Google)"
wrote:
> Trust me, we thought out all the scenarios. Here are the scenarios:
>
> 1. Just enable it in app.yaml
> - comple
+1 - I saw this design and immediately saw the tradeoffs-- hats off.
FYI even seasoned ops people occasionally need to "prove" that what's
in prod is actually what's in dev. As a real example, consider
bugs/
changes in your push scripts (in the case of GAE, wrappers for
appcfg)
It's like r
Excellent!
On Nov 19, 12:14 pm, Benjamin wrote:
> Really amazing.
> Can't wait to see it release officially.
--
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 unsubs
On Nov 22, 10:20 am, "Ikai Lan (Google)"
wrote:
> I'm seeing only 100-200 downloads of the prerelease SDKs, which you can
> download here:
> http://code.google.com/p/googleappengine/downloads/list
Ikai-- two bits of feedback...
1. Why so few downloads & feedback?
- no docs, and (I assume) no/f
looks like the server side is up:
check http://shell.appspot.com/
(screenshot) http://dl.dropbox.com/u/6919071/Captures/2010-12-01_2341.png
Google App Engine/1.4.0
Python 2.5.2 (r252:60911, May 12 2010, 14:18:27)
[GCC 4.3.1]
On Nov 30, 3:30 pm, Adam Sah wrote:
> On Nov 22, 10:20 am, "Ik
On Thursday, December 2, 2010 4:42:55 AM UTC, sophware wrote:looks like
the server side is up:
check http://shell.appspot.com/
(screenshot)
http://dl.dropbox.com/u/6919071/Captures/2010-12-01_2341.png
Google App Engine/1.4.0
Python 2.5.2 (r252:60911, May 12 2010, 14:18:27)
[GCC 4.3.1]
Thanks
Hi
Thanks for the news. There are many good features in this release -
but for me the most important one is that the development team have
obviously been listening to the feedback and tackling the issues which
matter
Great stuff
On Nov 18, 10:27 pm, "Ikai Lan (Google)"
wrote:
> Hey everyone,
>
Always On will be a paid feature you enable in the admin console.
I'll post some light sample code for channel API and warmup requests in a
bit.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitte
Awesome additions.
Are you able to share the pricing terms for Always On feature now?
Thanks!
On Thu, Nov 18, 2010 at 3:17 PM, Ikai Lan (Google)
> wrote:
> Always On will be a paid feature you enable in the admin console.
>
> I'll post some light sample code for channel API and warmup requests
I can't share the pricing yet - wait for the release.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine
On Thu, Nov 18, 2010 at 3:30 PM, Kangesh Gunaseelan wrot
It's not in the release notes, so I'd lean towards no, it didn't make it.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine
On Thu, Nov 18, 2010 at 4:38 PM, Ale
It's an amazing release, waiting for the docs.
--
keakon
On Fri, Nov 19, 2010 at 9:47 AM, Sergio Lopes wrote:
> Since I'm too excited to wait, I opened the new appengine-web.xsd in
> 1.4.0-pre to see how to configure the new features. There is a new
> tag with a boolean value. Of cours
Hi Julian,
Long running user facing requests are bad for the ecosystem, yes. Long
running background tasks, however, can be placed into a different execution
pool. Fast background tasks are placed into the same execution pool as your
web facing requests.
The rule of thumb here is to create differ
What are the consequences of a task being in the fast pool or the slow pool?
On Fri, Nov 19, 2010 at 1:07 PM, Ikai Lan (Google)
> wrote:
> Hi Julian,
>
> Long running user facing requests are bad for the ecosystem, yes. Long
> running background tasks, however, can be placed into a different exe
Web requests share the fast pool, so there is a chance you can block all
your web facing instances from serving web requests. Additionally, the
latency is averaged when considering whether or not to autoscale your
instances, so putting slow work in a fast queue would prevent App Engine
from adding
Zac,
You shouldn't see errors on requests to your initial 3 instances. If your
traffic grows at a semi linear pace, warmup requests will also start up
instances before you need them and users should very rarely have their
requests hit cold starts.
In our testing, we found that applications with e
Right now, I've basically been doing as little work as possible in a single
task-
Fetching an iCal file in one task and persisting it, enqueueing a task to
split it into single event snippets, and then each snippet gets processed in
it's own task.
With a 10-minute task queue, I could easily do al
Some of his points are perfectly valid; there are issues that deserve
attention. I think one or two of the points are out-of-date (eg 1,000
entity limit and _soon_ the 30 second background limit!).
Of course, about 1/2 of the complaints would not have been a surprise
if they spent 5 minutes and r
Nice work App Engine Team.
On Sun, Nov 21, 2010 at 8:54 PM, Jagan wrote:
> Hi
>
> - The deadline for Task Queue and Cron requests has been raised to 10
> minutes.
>
> Do you mean that now each Task Queue and Cron request can run for 10
> min, instead of the old 30 seconds limit??!
>
> Jagan
>
Hey,
A couple of questions were brought up in this thread. I'll do my best to
answer them:
- YES, task queues and cron jobs will now have a 10 minute limit, increased
from 30 seconds. Note that you still want to favor lots of small, quick
tasks when possible.
- I need to verify the behavior, but
Hi Ikai,
about your prerelease feedback request, generally speaking we need a
more direct way to suggest you SDK patches.
According to http://code.google.com/p/googleappengine/ we have to "post
the code for the patch in the issue".
But nothing can help you evaluating soon those patches because
If it's just 2 lines, you can post them in the group or create an issue and
let us know.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine
On Mon, Nov 22, 2010
Thank you for a great release!
Heavy frameworks like Spring MVC can be loaded really fast if you
serialize the context into cache/datastore. Unfortunately this is not
easy to do and I don't know if SpringSource is planning on making it
easier.
A blog post like that was bound to be published soone
Being a one time nuke, means its not possible to for a developer to
accidentally (or maliciously) re enable downloads :)
One of the main objections to 'download' is it makes it easier for
someone who shouldnt get their hands on the source code. Yes the fact
only the uploading developer gets it, ma
Yes, there is still a 30 second limit on web facing requests.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Reddit: http://www.reddit.com/r/appengine
Twitter: http://twitter.com/app_engine
On Wed, Nov 24, 2010 at 10:18 AM, Sekhar Ravinut
Trust me, we thought out all the scenarios. Here are the scenarios:
1. Just enable it in app.yaml
- completely useless from a security perspective, an attacker would just
enable it, download code, upload malicious code and steal data/compromise
users' data over time
2. Make it opt-in, so you can'
Hello Ikai,
We are not using as a source code control system, we have a core app on a
version, its duty is to aggregate and store data.
we have a team who are building modules which uses the data in the
datastore.
The core app contains some confidential info about the sources of the data,
whic
Don't worry about it, the developer can only download the source code
deployed by himself.
--
keakon
On Sat, Nov 27, 2010 at 1:53 AM, Sandeep Koduri wrote:
> Hello Ikai,
>
> We are not using as a source code control system, we have a core app on
> a version, its duty is to aggregate
Adam: good use case. Now that you mention it, I remember a situation in
which I've logged in remotely and diff'd deployed code vs. code that I
believed was deployed. In the end (as is usually the case in these
situations), I realized it was user error from a bad source code merge to a
branch.
Admi
Ikai, you wrote "'ll post some light sample code for channel API and warmup
requests in a bit."--
Has that stuff been posted somewhere yet?
On Thu, Nov 18, 2010 at 6:17 PM, Ikai Lan (Google)
> wrote:
> Always On will be a paid feature you enable in the admin console.
>
> I'll post some light sa
67 matches
Mail list logo
