Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Danny Tuppeny]

When you setup extra domains, they'll all just run the same scripts.
However in your scripts you can read the host header using:

os.environ.get('HTTP_HOST')

This will contain the full domain (eg. mysub.mydomain.com), which you
could use to do output different content.

Hope this helps,

Danny




On 15 February 2010 19:42, reallife  wrote:
> Quick question: I understand how to set up the custom wildcard domain
> (as described here: http://code.google.com/appengine/docs/domain.html)
> but I am unsure how to map this within my application. I could not
> find any Python code examples in the documentation. Any suggestions
> are very much appreciated! :)
>
> Thanks
>
> On Feb 13, 6:21 pm, Danny Tuppeny  wrote:
>> Excellent, thanks for pointing this out, I should've checked :-)
>>
>> On 13 February 2010 17:36, Barry Hunter  wrote:
>>
>>
>>
>> > From the documentation:
>>
>> > If you have administrator-only pages in your application that are used
>> > to administer the app, you can have those pages appear in the
>> > Administration Console. The Administration Console includes the name
>> > of the page in its sidebar, and displays the page in an HTML iframe.
>
> --
> 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.
>
>

-- 
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: App Engine SDK 1.3.1 is out!

[reallife]

Quick question: I understand how to set up the custom wildcard domain
(as described here: http://code.google.com/appengine/docs/domain.html)
but I am unsure how to map this within my application. I could not
find any Python code examples in the documentation. Any suggestions
are very much appreciated! :)

Thanks

On Feb 13, 6:21 pm, Danny Tuppeny  wrote:
> Excellent, thanks for pointing this out, I should've checked :-)
>
> On 13 February 2010 17:36, Barry Hunter  wrote:
>
>
>
> > From the documentation:
>
> > If you have administrator-only pages in your application that are used
> > to administer the app, you can have those pages appear in the
> > Administration Console. The Administration Console includes the name
> > of the page in its sidebar, and displays the page in an HTML iframe.

-- 
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.

Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Danny Tuppeny]

Excellent, thanks for pointing this out, I should've checked :-)

On 13 February 2010 17:36, Barry Hunter  wrote:
> From the documentation:
>
> If you have administrator-only pages in your application that are used
> to administer the app, you can have those pages appear in the
> Administration Console. The Administration Console includes the name
> of the page in its sidebar, and displays the page in an HTML iframe.

-- 
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.

Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Barry Hunter]

>From the documentation:

If you have administrator-only pages in your application that are used
to administer the app, you can have those pages appear in the
Administration Console. The Administration Console includes the name
of the page in its sidebar, and displays the page in an HTML iframe.



On 13 February 2010 11:02, Danny Tuppeny  wrote:
> I haven't had chance to try this yet, but does it load our pages
> inside a frame, or does it load full window and lose the App Engine
> admin nav?
>
> Would be cool if we could keep the nav, though I appreciate there's
> not really a nice way to do it.
>
> On Feb 11, 12:30 am, "David W."  wrote:
>> Picking through the diffs for 1.3.1, the syntax is:
>>
>> admin_console:
>>   pages:
>>     - url: /some/protected/url/in/your/app
>>       name: "My Stats Page"
>>
>>     - url: /some/protected/url/in/your/app2
>>       name: "My Stats Page 2"
>>
>> etc.
>
> --
> 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.
>
>

-- 
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: App Engine SDK 1.3.1 is out!

[Danny Tuppeny]

I haven't had chance to try this yet, but does it load our pages
inside a frame, or does it load full window and lose the App Engine
admin nav?

Would be cool if we could keep the nav, though I appreciate there's
not really a nice way to do it.

On Feb 11, 12:30 am, "David W."  wrote:
> Picking through the diffs for 1.3.1, the syntax is:
>
> admin_console:
>   pages:
>     - url: /some/protected/url/in/your/app
>       name: "My Stats Page"
>
>     - url: /some/protected/url/in/your/app2
>       name: "My Stats Page 2"
>
> etc.

-- 
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: App Engine SDK 1.3.1 is out!

[Stephen]

On Feb 12, 4:09 pm, ryan  wrote:
> On Feb 11, 6:53 am, Brandon Thomson  wrote:
>
>
>
> > The downside of extra latency for get()s is it means users will very
> > occasionally see the spinning beach ball for a long time instead of an
> > error page after 4 seconds in non-ajax applications. It's not a big
> > deal for AJAX handlers because we can choose a timeout and control the
> > experience client-side but for guys with a lot of non-AJAX html pages
> > it could be frustrating.
>
> very good point. happily, we're planning to expose a deadline
> parameter for most datastore calls soon, maybe as soon as 1.3.2.
> that should give you the flexibility to control which calls need to
> return fast and which can afford to run longer.


Are we charged for failed API calls?

-- 
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: App Engine SDK 1.3.1 is out!

[ryan]

On Feb 11, 6:53 am, Brandon Thomson  wrote:
>
> The downside of extra latency for get()s is it means users will very
> occasionally see the spinning beach ball for a long time instead of an
> error page after 4 seconds in non-ajax applications. It's not a big
> deal for AJAX handlers because we can choose a timeout and control the
> experience client-side but for guys with a lot of non-AJAX html pages
> it could be frustrating.

very good point. happily, we're planning to expose a deadline
parameter for most datastore calls soon, maybe as soon as 1.3.2.
that should give you the flexibility to control which calls need to
return fast and which can afford to run longer.

-- 
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: App Engine SDK 1.3.1 is out!

[nickmilon]

Great release  !
Let  MS Azure that officially started this week eat our dust now ;)

Happy (re)coding with all those new feaures.

Nick

On Feb 11, 4:53 pm, Brandon Thomson  wrote:
> not a batch; it was a get() of a single entity by Key and a put() of a
> single entity.
>
> The downside of extra latency for get()s is it means users will very
> occasionally see the spinning beach ball for a long time instead of an
> error page after 4 seconds in non-ajax applications. It's not a big
> deal for AJAX handlers because we can choose a timeout and control the
> experience client-side but for guys with a lot of non-AJAX html pages
> it could be frustrating.
>
> on the other hand, this is undoubtedly a huge improvement for the
> remote_api console. when using the console generally i just want
> whatever gets or puts to be retried whether it takes 10ms or 10
> minutes to finish. adding retry code manually every time was very
> annoying.
>
> On Feb 11, 5:28 am, Nickolas Daskalou  wrote:
>
>
>
> > Wow, that's huge. Was that a batch get/put (and if so, how many entities?),
> > or just for one single entity?
>
> > On 11 February 2010 21:19, Brandon Thomson  wrote:
>
> > > > though I am curious if we can predict how long .get()
> > > > and .fetch() will potentially block for? Seems like this used to be
> > > > around 4 seconds in the event of Timeout but I assume it may be longer
> > > > now.
>
> > > In case anyone is curious, I have logged a .get() that blocked for 21
> > > seconds and a .put() that blocked for 20.5 seconds. So the latency can
> > > be much higher now.
>
> > > --
> > > 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 > >  e...@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.

-- 
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: App Engine SDK 1.3.1 is out!

[Brandon Thomson]

not a batch; it was a get() of a single entity by Key and a put() of a
single entity.

The downside of extra latency for get()s is it means users will very
occasionally see the spinning beach ball for a long time instead of an
error page after 4 seconds in non-ajax applications. It's not a big
deal for AJAX handlers because we can choose a timeout and control the
experience client-side but for guys with a lot of non-AJAX html pages
it could be frustrating.

on the other hand, this is undoubtedly a huge improvement for the
remote_api console. when using the console generally i just want
whatever gets or puts to be retried whether it takes 10ms or 10
minutes to finish. adding retry code manually every time was very
annoying.

On Feb 11, 5:28 am, Nickolas Daskalou  wrote:
> Wow, that's huge. Was that a batch get/put (and if so, how many entities?),
> or just for one single entity?
>
> On 11 February 2010 21:19, Brandon Thomson  wrote:
>
>
>
>
>
> > > though I am curious if we can predict how long .get()
> > > and .fetch() will potentially block for? Seems like this used to be
> > > around 4 seconds in the event of Timeout but I assume it may be longer
> > > now.
>
> > In case anyone is curious, I have logged a .get() that blocked for 21
> > seconds and a .put() that blocked for 20.5 seconds. So the latency can
> > be much higher now.
>
> > --
> > 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 > e...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

-- 
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.

Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Nickolas Daskalou]

Wow, that's huge. Was that a batch get/put (and if so, how many entities?),
or just for one single entity?


On 11 February 2010 21:19, Brandon Thomson  wrote:

>
> > though I am curious if we can predict how long .get()
> > and .fetch() will potentially block for? Seems like this used to be
> > around 4 seconds in the event of Timeout but I assume it may be longer
> > now.
>
> In case anyone is curious, I have logged a .get() that blocked for 21
> seconds and a .put() that blocked for 20.5 seconds. So the latency can
> be much higher now.
>
> --
> 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.
>
>

-- 
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: App Engine SDK 1.3.1 is out!

[Brandon Thomson]

> though I am curious if we can predict how long .get()
> and .fetch() will potentially block for? Seems like this used to be
> around 4 seconds in the event of Timeout but I assume it may be longer
> now.

In case anyone is curious, I have logged a .get() that blocked for 21
seconds and a .put() that blocked for 20.5 seconds. So the latency can
be much higher now.

-- 
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: App Engine SDK 1.3.1 is out!

[Brandon Thomson]

love the custom admin pages! Works very well for my existing admin
pages with just an app.yaml change.

auto-retry is probably for the best now that writes can be easily
deferred with task-queue and request latency is not as big of a
concern. though I am curious if we can predict how long .get()
and .fetch() will potentially block for? Seems like this used to be
around 4 seconds in the event of Timeout but I assume it may be longer
now.

On Feb 11, 12:12 am, kang  wrote:
> cool!
>
> On Thu, Feb 11, 2010 at 7:15 AM, Ikai L (Google)  wrote:
>
>
>
>
>
> > Check it out!
>
> >http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
>
> > Here's
> > the post:
>
> > App Engine SDK 1.3.1, Including Major Improvements to 
> > Datastore!
> > We are excited to announce the release of version 1.3.1 of the App Engine
> > SDK for both Python and Java. While this release contains plenty of new
> > features and fixes, we've concentrated on using our very first SDK release
> > of 2010 to improve the heart of many App Engine applications: the Datastore.
>
> > Here are the three major improvements that 1.3.1 has in store for datastore
> > users:
>
> >    - *Datastore Query Cursors* - Cursors allow applications to save and
> >    'bookmark' their progress through a query, so that it can be resumed 
> > later.
> >    This works great in combination with paging URLs, as well as processing 
> > in
> >    the Task Queue API, but there are many other uses. Watch for an upcoming
> >    blog post that explores Cursors in the near future. They're also really
> >    handy in the context of the next change...
> >    - *No more 1000 result limit* - That's right: with addition of Cursors
> >    and the culmination of many smaller Datastore stability and performance
> >    improvements over the last few months, we're now confident enough to 
> > remove
> >    the maximum result limit altogether. Whether you're doing a fetch,
> >    iterating, or using a Cursor, there's no limits on the number of results.
> >    - *Reduced error rate with Automatic Datastore Retries* - We've heard a
> >    lot of feedback that you don't want to deal with the Datastore's sporadic
> >    errors. In response, App Engine now automatically retries all datastore
> >    calls (with the exception of transaction commits) when your applications
> >    encounters a datastore error caused by being unable to reach Bigtable.
> >    Datastore retries automatically builds in what many of you have been 
> > doing
> >    in your code already, and our tests have shown it drastically reduces the
> >    number of errors your application experiences (by up to *3-4x error
> >    reduction for puts, 10-30x for gets*).
>
> > But even with our focus on the Datastore, we were able to sneak in a quite
> > a number of other new goodies into 1.3.1 as well:
>
> > For Python, we've included the *AppStats* RPC instrumentation library.
> > AppStats lets users easily profile the performance of calls from their app
> > to the App Engine backend services to identify and isolate issues such as
> > ineffective caching, bottlenecks, and redundant RPC calls in their app. (A
> > Java version is in beta testing now.)
>
> > And for Java, we've included a comprehensive new *unit-testing framework* 
> > for
> > your App Engine apps. The unit-testing framework enables you to test your
> > application code in a natural, fully supported manner, and also allows you
> > to integrate your App Engine apps into other existing testing and automation
> > frameworks.
>
> > The list of changes in 1.3.1 goes on and on (Custom Admin Console pages!
> > Support for wildcard domain mappings! Java precompilation on by default for
> > all applications!), so make sure to 
> > download the
> > new version and read our release notes for the complete list 
> > (Python
> > , Java
> > ).
>
> > Posted by the App Engine Team
>
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> >http://googleappengine.blogspot.com|http://twitter.com/app_engine
>
> > --
> > 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 > e...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> Stay hungry,Stay foolish.

-- 
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.co

Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Nickolas Daskalou]

Yeah, this is a great release. Well done Google dudes and dudettes!


On 11 February 2010 15:32, gops  wrote:

> Wow!!! with wildcard and cursor , all thing i need is available, yay!!
> ( of course map reduce remains,,,but i sense it coming soon.. )
>
> On Feb 11, 5:38 am, "appengine-s...@google.com"  s...@google.com> wrote:
> > For more information on wildcard domain mappings see:
> http://code.google.com/appengine/docs/domain.html
> >
> > For more information on custom admin console pages see:
> > Java:
> http://code.google.com/appengine/docs/java/config/appconfig.html#Admi...
> > Python:
> http://code.google.com/appengine/docs/python/config/appconfig.html#Ad...
> >
> > On Feb 10, 4:30 pm, "David W."  wrote:
> >
> >
> >
> > > On Feb 10, 11:45 pm, Koen Bok  wrote:
> >
> > > > Great update!
> >
> > > > Where can we find more info about:
> >
> > > > -CustomAdminConsole pages
> >
> > > Picking through the diffs for 1.3.1, the syntax is:
> >
> > > admin_console:
> > >   pages:
> > > - url: /some/protected/url/in/your/app
> > >   name: "My Stats Page"
> >
> > > - url: /some/protected/url/in/your/app2
> > >   name: "My Stats Page 2"
> >
> > > etc.
> >
> > > The extra pages then appear in the column on the left-hand side of the
> > > admin panel, under the billing section.
> >
> > > > - Support for wildcard domain mappings
> >
> > > > On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
> >
> > > > > Check it out!
> >
> > > > >
> http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
> >
> > > > > <
> http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ..
> .>Here's
> > > > > the post:
> >
> > > > > App Engine SDK 1.3.1, Including Major Improvements to
> > > > > Datastore!<
> http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...>
> > > > > We are excited to announce the release of version 1.3.1 of the App
> Engine
> > > > > SDK for both Python and Java. While this release contains plenty of
> new
> > > > > features and fixes, we've concentrated on using our very first SDK
> release
> > > > > of 2010 to improve the heart of many App Engine applications: the
> Datastore.
> >
> > > > > Here are the three major improvements that 1.3.1 has in store for
> datastore
> > > > > users:
> >
> > > > >- *Datastore Query Cursors* - Cursors allow applications to save
> and
> > > > >'bookmark' their progress through a query, so that it can be
> resumed later.
> > > > >This works great in combination with paging URLs, as well as
> processing in
> > > > >the Task Queue API, but there are many other uses. Watch for an
> upcoming
> > > > >blog post that explores Cursors in the near future. They're also
> really
> > > > >handy in the context of the next change...
> > > > >- *No more 1000 result limit* - That's right: with addition of
> Cursors
> > > > >and the culmination of many smaller Datastore stability and
> performance
> > > > >improvements over the last few months, we're now confident
> enough to remove
> > > > >the maximum result limit altogether. Whether you're doing a
> fetch,
> > > > >iterating, or using a Cursor, there's no limits on the number of
> results.
> > > > >- *Reduced error rate with Automatic Datastore Retries* - We've
> heard a
> > > > >lot of feedback that you don't want to deal with the Datastore's
> sporadic
> > > > >errors. In response, App Engine now automatically retries all
> datastore
> > > > >calls (with the exception of transaction commits) when your
> applications
> > > > >encounters a datastore error caused by being unable to reach
> Bigtable.
> > > > >Datastore retries automatically builds in what many of you have
> been doing
> > > > >in your code already, and our tests have shown it drastically
> reduces the
> > > > >number of errors your application experiences (by up to *3-4x
> error
> > > > >reduction for puts, 10-30x for gets*).
> >
> > > > > But even with our focus on the Datastore, we were able to sneak in
> a quite a
> > > > > number of other new goodies into 1.3.1 as well:
> >
> > > > > For Python, we've included the *AppStats* RPC instrumentation
> library.
> > > > > AppStats lets users easily profile the performance of calls from
> their app
> > > > > to the App Engine backend services to identify and isolate issues
> such as
> > > > > ineffective caching, bottlenecks, and redundant RPC calls in their
> app. (A
> > > > > Java version is in beta testing now.)
> >
> > > > > And for Java, we've included a comprehensive new *unit-testing
> framework* for
> > > > > your App Engine apps. The unit-testing framework enables you to
> test your
> > > > > application code in a natural, fully supported manner, and also
> allows you
> > > > > to integrate your App Engine apps into other existing testing and
> automation
> > > > > frameworks.
> >
> > > > > The list of changes in 1.3.1 goes on and on (CustomAdminConsole
> pages!
> > > > > Support for wildcar

[google-appengine] Re: App Engine SDK 1.3.1 is out!

[gops]

Wow!!! with wildcard and cursor , all thing i need is available, yay!!
( of course map reduce remains,,,but i sense it coming soon.. )

On Feb 11, 5:38 am, "appengine-s...@google.com"  wrote:
> For more information on wildcard domain mappings 
> see:http://code.google.com/appengine/docs/domain.html
>
> For more information on custom admin console pages see:
> Java:http://code.google.com/appengine/docs/java/config/appconfig.html#Admi...
> Python:http://code.google.com/appengine/docs/python/config/appconfig.html#Ad...
>
> On Feb 10, 4:30 pm, "David W."  wrote:
>
>
>
> > On Feb 10, 11:45 pm, Koen Bok  wrote:
>
> > > Great update!
>
> > > Where can we find more info about:
>
> > > -CustomAdminConsole pages
>
> > Picking through the diffs for 1.3.1, the syntax is:
>
> > admin_console:
> >   pages:
> >     - url: /some/protected/url/in/your/app
> >       name: "My Stats Page"
>
> >     - url: /some/protected/url/in/your/app2
> >       name: "My Stats Page 2"
>
> > etc.
>
> > The extra pages then appear in the column on the left-hand side of the
> > admin panel, under the billing section.
>
> > > - Support for wildcard domain mappings
>
> > > On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
>
> > > > Check it out!
>
> > > >http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
>
> > > > Here's
> > > > the post:
>
> > > > App Engine SDK 1.3.1, Including Major Improvements to
> > > > Datastore!
> > > > We are excited to announce the release of version 1.3.1 of the App 
> > > > Engine
> > > > SDK for both Python and Java. While this release contains plenty of new
> > > > features and fixes, we've concentrated on using our very first SDK 
> > > > release
> > > > of 2010 to improve the heart of many App Engine applications: the 
> > > > Datastore.
>
> > > > Here are the three major improvements that 1.3.1 has in store for 
> > > > datastore
> > > > users:
>
> > > >    - *Datastore Query Cursors* - Cursors allow applications to save and
> > > >    'bookmark' their progress through a query, so that it can be resumed 
> > > > later.
> > > >    This works great in combination with paging URLs, as well as 
> > > > processing in
> > > >    the Task Queue API, but there are many other uses. Watch for an 
> > > > upcoming
> > > >    blog post that explores Cursors in the near future. They're also 
> > > > really
> > > >    handy in the context of the next change...
> > > >    - *No more 1000 result limit* - That's right: with addition of 
> > > > Cursors
> > > >    and the culmination of many smaller Datastore stability and 
> > > > performance
> > > >    improvements over the last few months, we're now confident enough to 
> > > > remove
> > > >    the maximum result limit altogether. Whether you're doing a fetch,
> > > >    iterating, or using a Cursor, there's no limits on the number of 
> > > > results.
> > > >    - *Reduced error rate with Automatic Datastore Retries* - We've 
> > > > heard a
> > > >    lot of feedback that you don't want to deal with the Datastore's 
> > > > sporadic
> > > >    errors. In response, App Engine now automatically retries all 
> > > > datastore
> > > >    calls (with the exception of transaction commits) when your 
> > > > applications
> > > >    encounters a datastore error caused by being unable to reach 
> > > > Bigtable.
> > > >    Datastore retries automatically builds in what many of you have been 
> > > > doing
> > > >    in your code already, and our tests have shown it drastically 
> > > > reduces the
> > > >    number of errors your application experiences (by up to *3-4x error
> > > >    reduction for puts, 10-30x for gets*).
>
> > > > But even with our focus on the Datastore, we were able to sneak in a 
> > > > quite a
> > > > number of other new goodies into 1.3.1 as well:
>
> > > > For Python, we've included the *AppStats* RPC instrumentation library.
> > > > AppStats lets users easily profile the performance of calls from their 
> > > > app
> > > > to the App Engine backend services to identify and isolate issues such 
> > > > as
> > > > ineffective caching, bottlenecks, and redundant RPC calls in their app. 
> > > > (A
> > > > Java version is in beta testing now.)
>
> > > > And for Java, we've included a comprehensive new *unit-testing 
> > > > framework* for
> > > > your App Engine apps. The unit-testing framework enables you to test 
> > > > your
> > > > application code in a natural, fully supported manner, and also allows 
> > > > you
> > > > to integrate your App Engine apps into other existing testing and 
> > > > automation
> > > > frameworks.
>
> > > > The list of changes in 1.3.1 goes on and on (CustomAdminConsole pages!
> > > > Support for wildcard domain mappings! Java precompilation on by default 
> > > > for
> > > > all applications!), so make sure to
> > > > download

[google-appengine] Re: App Engine SDK 1.3.1 is out!

[appengine-s...@google.com]

For more information on wildcard domain mappings see:
http://code.google.com/appengine/docs/domain.html

For more information on custom admin console pages see:
Java: 
http://code.google.com/appengine/docs/java/config/appconfig.html#Administration_Console_Custom_Pages
Python: 
http://code.google.com/appengine/docs/python/config/appconfig.html#Administration_Console_Custom_Pages

On Feb 10, 4:30 pm, "David W."  wrote:
> On Feb 10, 11:45 pm, Koen Bok  wrote:
>
> > Great update!
>
> > Where can we find more info about:
>
> > -CustomAdminConsole pages
>
> Picking through the diffs for 1.3.1, the syntax is:
>
> admin_console:
>   pages:
>     - url: /some/protected/url/in/your/app
>       name: "My Stats Page"
>
>     - url: /some/protected/url/in/your/app2
>       name: "My Stats Page 2"
>
> etc.
>
> The extra pages then appear in the column on the left-hand side of the
> admin panel, under the billing section.
>
> > - Support for wildcard domain mappings
>
> > On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
>
> > > Check it out!
>
> > >http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
>
> > > Here's
> > > the post:
>
> > > App Engine SDK 1.3.1, Including Major Improvements to
> > > Datastore!
> > > We are excited to announce the release of version 1.3.1 of the App Engine
> > > SDK for both Python and Java. While this release contains plenty of new
> > > features and fixes, we've concentrated on using our very first SDK release
> > > of 2010 to improve the heart of many App Engine applications: the 
> > > Datastore.
>
> > > Here are the three major improvements that 1.3.1 has in store for 
> > > datastore
> > > users:
>
> > >    - *Datastore Query Cursors* - Cursors allow applications to save and
> > >    'bookmark' their progress through a query, so that it can be resumed 
> > > later.
> > >    This works great in combination with paging URLs, as well as 
> > > processing in
> > >    the Task Queue API, but there are many other uses. Watch for an 
> > > upcoming
> > >    blog post that explores Cursors in the near future. They're also really
> > >    handy in the context of the next change...
> > >    - *No more 1000 result limit* - That's right: with addition of Cursors
> > >    and the culmination of many smaller Datastore stability and performance
> > >    improvements over the last few months, we're now confident enough to 
> > > remove
> > >    the maximum result limit altogether. Whether you're doing a fetch,
> > >    iterating, or using a Cursor, there's no limits on the number of 
> > > results.
> > >    - *Reduced error rate with Automatic Datastore Retries* - We've heard a
> > >    lot of feedback that you don't want to deal with the Datastore's 
> > > sporadic
> > >    errors. In response, App Engine now automatically retries all datastore
> > >    calls (with the exception of transaction commits) when your 
> > > applications
> > >    encounters a datastore error caused by being unable to reach Bigtable.
> > >    Datastore retries automatically builds in what many of you have been 
> > > doing
> > >    in your code already, and our tests have shown it drastically reduces 
> > > the
> > >    number of errors your application experiences (by up to *3-4x error
> > >    reduction for puts, 10-30x for gets*).
>
> > > But even with our focus on the Datastore, we were able to sneak in a 
> > > quite a
> > > number of other new goodies into 1.3.1 as well:
>
> > > For Python, we've included the *AppStats* RPC instrumentation library.
> > > AppStats lets users easily profile the performance of calls from their app
> > > to the App Engine backend services to identify and isolate issues such as
> > > ineffective caching, bottlenecks, and redundant RPC calls in their app. (A
> > > Java version is in beta testing now.)
>
> > > And for Java, we've included a comprehensive new *unit-testing framework* 
> > > for
> > > your App Engine apps. The unit-testing framework enables you to test your
> > > application code in a natural, fully supported manner, and also allows you
> > > to integrate your App Engine apps into other existing testing and 
> > > automation
> > > frameworks.
>
> > > The list of changes in 1.3.1 goes on and on (CustomAdminConsole pages!
> > > Support for wildcard domain mappings! Java precompilation on by default 
> > > for
> > > all applications!), so make sure to
> > > download the
> > > new version and read our release notes for the complete list
> > > (Python
> > > , 
> > > Java
> > > ).
>
> > > Posted by the App Engine Team
>
> > > --
> > > Ikai Lan
> > > Developer Programs Engineer, Google App 
> > > Enginehttp://googleappengine.blogspot.com|htt

[google-appengine] Re: App Engine SDK 1.3.1 is out!

[David W.]

On Feb 10, 11:45 pm, Koen Bok  wrote:
> Great update!
>
> Where can we find more info about:
>
> -CustomAdminConsole pages

Picking through the diffs for 1.3.1, the syntax is:


admin_console:
  pages:
- url: /some/protected/url/in/your/app
  name: "My Stats Page"

- url: /some/protected/url/in/your/app2
  name: "My Stats Page 2"

etc.

The extra pages then appear in the column on the left-hand side of the
admin panel, under the billing section.


> - Support for wildcard domain mappings
>
> On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
>
> > Check it out!
>
> >http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
>
> > Here's
> > the post:
>
> > App Engine SDK 1.3.1, Including Major Improvements to
> > Datastore!
> > We are excited to announce the release of version 1.3.1 of the App Engine
> > SDK for both Python and Java. While this release contains plenty of new
> > features and fixes, we've concentrated on using our very first SDK release
> > of 2010 to improve the heart of many App Engine applications: the Datastore.
>
> > Here are the three major improvements that 1.3.1 has in store for datastore
> > users:
>
> >    - *Datastore Query Cursors* - Cursors allow applications to save and
> >    'bookmark' their progress through a query, so that it can be resumed 
> > later.
> >    This works great in combination with paging URLs, as well as processing 
> > in
> >    the Task Queue API, but there are many other uses. Watch for an upcoming
> >    blog post that explores Cursors in the near future. They're also really
> >    handy in the context of the next change...
> >    - *No more 1000 result limit* - That's right: with addition of Cursors
> >    and the culmination of many smaller Datastore stability and performance
> >    improvements over the last few months, we're now confident enough to 
> > remove
> >    the maximum result limit altogether. Whether you're doing a fetch,
> >    iterating, or using a Cursor, there's no limits on the number of results.
> >    - *Reduced error rate with Automatic Datastore Retries* - We've heard a
> >    lot of feedback that you don't want to deal with the Datastore's sporadic
> >    errors. In response, App Engine now automatically retries all datastore
> >    calls (with the exception of transaction commits) when your applications
> >    encounters a datastore error caused by being unable to reach Bigtable.
> >    Datastore retries automatically builds in what many of you have been 
> > doing
> >    in your code already, and our tests have shown it drastically reduces the
> >    number of errors your application experiences (by up to *3-4x error
> >    reduction for puts, 10-30x for gets*).
>
> > But even with our focus on the Datastore, we were able to sneak in a quite a
> > number of other new goodies into 1.3.1 as well:
>
> > For Python, we've included the *AppStats* RPC instrumentation library.
> > AppStats lets users easily profile the performance of calls from their app
> > to the App Engine backend services to identify and isolate issues such as
> > ineffective caching, bottlenecks, and redundant RPC calls in their app. (A
> > Java version is in beta testing now.)
>
> > And for Java, we've included a comprehensive new *unit-testing framework* 
> > for
> > your App Engine apps. The unit-testing framework enables you to test your
> > application code in a natural, fully supported manner, and also allows you
> > to integrate your App Engine apps into other existing testing and automation
> > frameworks.
>
> > The list of changes in 1.3.1 goes on and on (CustomAdminConsole pages!
> > Support for wildcard domain mappings! Java precompilation on by default for
> > all applications!), so make sure to
> > download the
> > new version and read our release notes for the complete list
> > (Python
> > , Java
> > ).
>
> > Posted by the App Engine Team
>
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App 
> > Enginehttp://googleappengine.blogspot.com|http://twitter.com/app_engine

-- 
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.

Re: [google-appengine] Re: App Engine SDK 1.3.1 is out!

[Ross M Karchner]

I just tested wildcard domains--

When you are attaching a subdomain to your app, you can specify "*", which
will match all subdomains.

For this to reach maximum coolness, your registrar would have to support
wildcard CNAMES, it appears godaddy doesn't.

On Wed, Feb 10, 2010 at 6:45 PM, Koen Bok  wrote:

> Great update!
>
> Where can we find more info about:
>
> - Custom Admin Console pages
> - Support for wildcard domain mappings
>
> On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
> > Check it out!
> >
> > http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
> >
> >  .>Here's
> > the post:
> >
> > App Engine SDK 1.3.1, Including Major Improvements to
> > Datastore!<
> http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...>
> > We are excited to announce the release of version 1.3.1 of the App Engine
> > SDK for both Python and Java. While this release contains plenty of new
> > features and fixes, we've concentrated on using our very first SDK
> release
> > of 2010 to improve the heart of many App Engine applications: the
> Datastore.
> >
> > Here are the three major improvements that 1.3.1 has in store for
> datastore
> > users:
> >
> >- *Datastore Query Cursors* - Cursors allow applications to save and
> >'bookmark' their progress through a query, so that it can be resumed
> later.
> >This works great in combination with paging URLs, as well as
> processing in
> >the Task Queue API, but there are many other uses. Watch for an
> upcoming
> >blog post that explores Cursors in the near future. They're also
> really
> >handy in the context of the next change...
> >- *No more 1000 result limit* - That's right: with addition of Cursors
> >and the culmination of many smaller Datastore stability and
> performance
> >improvements over the last few months, we're now confident enough to
> remove
> >the maximum result limit altogether. Whether you're doing a fetch,
> >iterating, or using a Cursor, there's no limits on the number of
> results.
> >- *Reduced error rate with Automatic Datastore Retries* - We've heard
> a
> >lot of feedback that you don't want to deal with the Datastore's
> sporadic
> >errors. In response, App Engine now automatically retries all
> datastore
> >calls (with the exception of transaction commits) when your
> applications
> >encounters a datastore error caused by being unable to reach Bigtable.
> >Datastore retries automatically builds in what many of you have been
> doing
> >in your code already, and our tests have shown it drastically reduces
> the
> >number of errors your application experiences (by up to *3-4x error
> >reduction for puts, 10-30x for gets*).
> >
> > But even with our focus on the Datastore, we were able to sneak in a
> quite a
> > number of other new goodies into 1.3.1 as well:
> >
> > For Python, we've included the *AppStats* RPC instrumentation library.
> > AppStats lets users easily profile the performance of calls from their
> app
> > to the App Engine backend services to identify and isolate issues such as
> > ineffective caching, bottlenecks, and redundant RPC calls in their app.
> (A
> > Java version is in beta testing now.)
> >
> > And for Java, we've included a comprehensive new *unit-testing framework*
> for
> > your App Engine apps. The unit-testing framework enables you to test your
> > application code in a natural, fully supported manner, and also allows
> you
> > to integrate your App Engine apps into other existing testing and
> automation
> > frameworks.
> >
> > The list of changes in 1.3.1 goes on and on (Custom Admin Console pages!
> > Support for wildcard domain mappings! Java precompilation on by default
> for
> > all applications!), so make sure to
> > download the
> > new version and read our release notes for the complete list
> > (Python
> > , Java<
> http://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes>
> > ).
> >
> > Posted by the App Engine Team
> >
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Enginehttp://
> googleappengine.blogspot.com|http://twitter.com/app_engine
>
> --
> 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.
>
>

-- 
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.

[google-appengine] Re: App Engine SDK 1.3.1 is out!

[Koen Bok]

Great update!

Where can we find more info about:

- Custom Admin Console pages
- Support for wildcard domain mappings

On Feb 11, 12:15 am, "Ikai L (Google)"  wrote:
> Check it out!
>
> http://googleappengine.blogspot.com/2010/02/app-engine-sdk-131-includ...
>
> Here's
> the post:
>
> App Engine SDK 1.3.1, Including Major Improvements to
> Datastore!
> We are excited to announce the release of version 1.3.1 of the App Engine
> SDK for both Python and Java. While this release contains plenty of new
> features and fixes, we've concentrated on using our very first SDK release
> of 2010 to improve the heart of many App Engine applications: the Datastore.
>
> Here are the three major improvements that 1.3.1 has in store for datastore
> users:
>
>    - *Datastore Query Cursors* - Cursors allow applications to save and
>    'bookmark' their progress through a query, so that it can be resumed later.
>    This works great in combination with paging URLs, as well as processing in
>    the Task Queue API, but there are many other uses. Watch for an upcoming
>    blog post that explores Cursors in the near future. They're also really
>    handy in the context of the next change...
>    - *No more 1000 result limit* - That's right: with addition of Cursors
>    and the culmination of many smaller Datastore stability and performance
>    improvements over the last few months, we're now confident enough to remove
>    the maximum result limit altogether. Whether you're doing a fetch,
>    iterating, or using a Cursor, there's no limits on the number of results.
>    - *Reduced error rate with Automatic Datastore Retries* - We've heard a
>    lot of feedback that you don't want to deal with the Datastore's sporadic
>    errors. In response, App Engine now automatically retries all datastore
>    calls (with the exception of transaction commits) when your applications
>    encounters a datastore error caused by being unable to reach Bigtable.
>    Datastore retries automatically builds in what many of you have been doing
>    in your code already, and our tests have shown it drastically reduces the
>    number of errors your application experiences (by up to *3-4x error
>    reduction for puts, 10-30x for gets*).
>
> But even with our focus on the Datastore, we were able to sneak in a quite a
> number of other new goodies into 1.3.1 as well:
>
> For Python, we've included the *AppStats* RPC instrumentation library.
> AppStats lets users easily profile the performance of calls from their app
> to the App Engine backend services to identify and isolate issues such as
> ineffective caching, bottlenecks, and redundant RPC calls in their app. (A
> Java version is in beta testing now.)
>
> And for Java, we've included a comprehensive new *unit-testing framework* for
> your App Engine apps. The unit-testing framework enables you to test your
> application code in a natural, fully supported manner, and also allows you
> to integrate your App Engine apps into other existing testing and automation
> frameworks.
>
> The list of changes in 1.3.1 goes on and on (Custom Admin Console pages!
> Support for wildcard domain mappings! Java precompilation on by default for
> all applications!), so make sure to
> download the
> new version and read our release notes for the complete list
> (Python
> , Java
> ).
>
> Posted by the App Engine Team
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App 
> Enginehttp://googleappengine.blogspot.com|http://twitter.com/app_engine

-- 
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.