[google-appengine] Re: Access-Control-Allow-Origin error when accessing pages with admin requirement

[Xi Shen]

Sorry, in the app.yaml it should be "login: admin" :)


On Wednesday, July 30, 2014 2:13:51 PM UTC+10, Xi Shen wrote:
>
> Hi,
>
> I build a simple blog site of my own, and it has a admin entrance 
> https://davidshen84.appspot.com/blog/admin/. This url is set to "require: 
> admin" in the app.yaml, and only my account has access to it. This page 
> works fine in the past, and works works on the latest dev_server. But 
> online, when I try to access url, I saw below error in Chrome's console.
>
> XMLHttpRequest cannot load 
>> https://www.google.com/accounts/ServiceLogin?service=ah&passive=true&contin…EJsb2cMEgJhaCIUkEhbBFmCc7OK73FNDhSUJ_TIdsgoATIUS9ZyokjQBd6r_4fpSehJGMuA0TQ
>>  
>> .
>>  
>> No 'Access-Control-Allow-Origin' header is present on the requested 
>> resource. Origin 'https://davidshen84.appspot.com' is therefore not 
>> allowed access.
>
>
> I also post my question at 
> https://stackoverflow.com/questions/24925070/gae-app-login-is-blocked-by-cross-origin-access.
>  
> The app is developed using python, but I don't think this problem has 
> anything to do with the language.
>
> I think there might be some configuration changed in GAE admin console. I 
> review the latest document, and checked the admin console. I still have no 
> idea what is the cause. 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Access-Control-Allow-Origin error when accessing pages with admin requirement

[Xi Shen]

Hi,

I build a simple blog site of my own, and it has a admin 
entrance https://davidshen84.appspot.com/blog/admin/. This url is set to 
"require: admin" in the app.yaml, and only my account has access to it. 
This page works fine in the past, and works works on the latest dev_server. 
But online, when I try to access url, I saw below error in Chrome's console.

XMLHttpRequest cannot load 
> https://www.google.com/accounts/ServiceLogin?service=ah&passive=true&contin…EJsb2cMEgJhaCIUkEhbBFmCc7OK73FNDhSUJ_TIdsgoATIUS9ZyokjQBd6r_4fpSehJGMuA0TQ
>  
> .
>  
> No 'Access-Control-Allow-Origin' header is present on the requested 
> resource. Origin 'https://davidshen84.appspot.com' is therefore not 
> allowed access.


I also post my question at 
https://stackoverflow.com/questions/24925070/gae-app-login-is-blocked-by-cross-origin-access.
 
The app is developed using python, but I don't think this problem has 
anything to do with the language.

I think there might be some configuration changed in GAE admin console. I 
review the latest document, and checked the admin console. I still have no 
idea what is the cause. 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 500 server error on App Engine when using OpenID Users API on custom domain

[Joel E]

Well I was playing around with the "/main.jsp" part of the above code to 
see if I could get something working and oddly enough it seems that adding 
the custom domain to it fixes the 500 error without messing it up on 
appspot! Thanks for the help!

On Tuesday, July 29, 2014 7:35:03 PM UTC-4, Joel E wrote:
>
> Oh, I think I understand but I don't think it solves the issue. See, the 
> App Engine user's API accepts relative URLs and then takes care of 
> processing the call to the openID provider. Here's how my code works:
>
> String LogInURL = userService.createLoginURL("/main.jsp", null, 
> openid_identifier, null);
> resp.sendRedirect(LogInURL);
> I take the URL of the provider from the user (openid_identifier) and send 
> it to the App Engine Users API to create a redirect URL. Then I send the 
> user to the provider through that URL. The user first logs in through their 
> provider but on return to my app they land on a 500 error page instead of 
> being redirected through to /main.jsp. If I start the process from my 
> appspot.com domain instead it goes through to /main.jsp just fine.
>
> Thanks for trying though!
>
> On Tuesday, July 29, 2014 7:07:09 PM UTC-4, Mihail Russu wrote:
>>
>> Most OAuth providers require you to specify full callback url (in the 
>> request headers as well as in the control panel of their websites) so when 
>> changing domains you'd also need to update the URL on their end but I 
>> didn't realize until now that you are having issues with OpenID and NOT 
>> with OAuth, I am not sure if it's the same there.
>>
>> On Tuesday, July 29, 2014 5:18:29 PM UTC-5, Joel E wrote:
>>>
>>> Could you explain what you mean by the callback/redirect URL? I didn't 
>>> read anything about that in the documentation. Also, nothing from the error 
>>> appears in the logs since the crash happens in app engine's internal code.
>>>
>>> Thanks!
>>>
>>> On Tuesday, July 29, 2014 6:05:42 PM UTC-4, Mihail Russu wrote:

 Are there any error details in the Logs section that you can provide?

 Just last Friday I transferred an app from .appspot.com to a custom 
 domain and everything worked great as soon as I changed the 
 callback/redirect URLs on OAuth providers' end. Could it be that you 
 simply 
 forgot to update them? (this is unlikely to cause a 500 on AppEngine's end 
 but it's a start)

 Mihail.

 On Tuesday, July 29, 2014 12:41:29 PM UTC-5, Joel E wrote:
>
> I posted the details of this issue on StackOverflow here 
> 
>  
> but basically the Users API is crashing when accessed by an app running 
> on 
> a custom domain. I have not been able to get any help with this issue and 
> it would be great to get an answer from someone at Google as this seems 
> to 
> be an issue with App Engine's internal code. I'd be happy for any 
> suggestions or help at this point though.
>
> Thanks!
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 500 server error on App Engine when using OpenID Users API on custom domain

[Joel E]

Oh, I think I understand but I don't think it solves the issue. See, the 
App Engine user's API accepts relative URLs and then takes care of 
processing the call to the openID provider. Here's how my code works:

String LogInURL = userService.createLoginURL("/main.jsp", null, 
openid_identifier, null);
resp.sendRedirect(LogInURL);
I take the URL of the provider from the user (openid_identifier) and send 
it to the App Engine Users API to create a redirect URL. Then I send the 
user to the provider through that URL. The user first logs in through their 
provider but on return to my app they land on a 500 error page instead of 
being redirected through to /main.jsp. If I start the process from my 
appspot.com domain instead it goes through to /main.jsp just fine.

Thanks for trying though!

On Tuesday, July 29, 2014 7:07:09 PM UTC-4, Mihail Russu wrote:
>
> Most OAuth providers require you to specify full callback url (in the 
> request headers as well as in the control panel of their websites) so when 
> changing domains you'd also need to update the URL on their end but I 
> didn't realize until now that you are having issues with OpenID and NOT 
> with OAuth, I am not sure if it's the same there.
>
> On Tuesday, July 29, 2014 5:18:29 PM UTC-5, Joel E wrote:
>>
>> Could you explain what you mean by the callback/redirect URL? I didn't 
>> read anything about that in the documentation. Also, nothing from the error 
>> appears in the logs since the crash happens in app engine's internal code.
>>
>> Thanks!
>>
>> On Tuesday, July 29, 2014 6:05:42 PM UTC-4, Mihail Russu wrote:
>>>
>>> Are there any error details in the Logs section that you can provide?
>>>
>>> Just last Friday I transferred an app from .appspot.com to a custom 
>>> domain and everything worked great as soon as I changed the 
>>> callback/redirect URLs on OAuth providers' end. Could it be that you simply 
>>> forgot to update them? (this is unlikely to cause a 500 on AppEngine's end 
>>> but it's a start)
>>>
>>> Mihail.
>>>
>>> On Tuesday, July 29, 2014 12:41:29 PM UTC-5, Joel E wrote:

 I posted the details of this issue on StackOverflow here 
 
  
 but basically the Users API is crashing when accessed by an app running on 
 a custom domain. I have not been able to get any help with this issue and 
 it would be great to get an answer from someone at Google as this seems to 
 be an issue with App Engine's internal code. I'd be happy for any 
 suggestions or help at this point though.

 Thanks!

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 500 server error on App Engine when using OpenID Users API on custom domain

[Mihail Russu]

Most OAuth providers require you to specify full callback url (in the 
request headers as well as in the control panel of their websites) so when 
changing domains you'd also need to update the URL on their end but I 
didn't realize until now that you are having issues with OpenID and NOT 
with OAuth, I am not sure if it's the same there.

On Tuesday, July 29, 2014 5:18:29 PM UTC-5, Joel E wrote:
>
> Could you explain what you mean by the callback/redirect URL? I didn't 
> read anything about that in the documentation. Also, nothing from the error 
> appears in the logs since the crash happens in app engine's internal code.
>
> Thanks!
>
> On Tuesday, July 29, 2014 6:05:42 PM UTC-4, Mihail Russu wrote:
>>
>> Are there any error details in the Logs section that you can provide?
>>
>> Just last Friday I transferred an app from .appspot.com to a custom 
>> domain and everything worked great as soon as I changed the 
>> callback/redirect URLs on OAuth providers' end. Could it be that you simply 
>> forgot to update them? (this is unlikely to cause a 500 on AppEngine's end 
>> but it's a start)
>>
>> Mihail.
>>
>> On Tuesday, July 29, 2014 12:41:29 PM UTC-5, Joel E wrote:
>>>
>>> I posted the details of this issue on StackOverflow here 
>>> 
>>>  
>>> but basically the Users API is crashing when accessed by an app running on 
>>> a custom domain. I have not been able to get any help with this issue and 
>>> it would be great to get an answer from someone at Google as this seems to 
>>> be an issue with App Engine's internal code. I'd be happy for any 
>>> suggestions or help at this point though.
>>>
>>> Thanks!
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 500 server error on App Engine when using OpenID Users API on custom domain

[Joel E]

Could you explain what you mean by the callback/redirect URL? I didn't read 
anything about that in the documentation. Also, nothing from the error 
appears in the logs since the crash happens in app engine's internal code.

Thanks!

On Tuesday, July 29, 2014 6:05:42 PM UTC-4, Mihail Russu wrote:
>
> Are there any error details in the Logs section that you can provide?
>
> Just last Friday I transferred an app from .appspot.com to a custom 
> domain and everything worked great as soon as I changed the 
> callback/redirect URLs on OAuth providers' end. Could it be that you simply 
> forgot to update them? (this is unlikely to cause a 500 on AppEngine's end 
> but it's a start)
>
> Mihail.
>
> On Tuesday, July 29, 2014 12:41:29 PM UTC-5, Joel E wrote:
>>
>> I posted the details of this issue on StackOverflow here 
>> 
>>  
>> but basically the Users API is crashing when accessed by an app running on 
>> a custom domain. I have not been able to get any help with this issue and 
>> it would be great to get an answer from someone at Google as this seems to 
>> be an issue with App Engine's internal code. I'd be happy for any 
>> suggestions or help at this point though.
>>
>> Thanks!
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: 500 server error on App Engine when using OpenID Users API on custom domain

[Mihail Russu]

Are there any error details in the Logs section that you can provide?

Just last Friday I transferred an app from .appspot.com to a custom domain 
and everything worked great as soon as I changed the callback/redirect URLs 
on OAuth providers' end. Could it be that you simply forgot to update them? 
(this is unlikely to cause a 500 on AppEngine's end but it's a start)

Mihail.

On Tuesday, July 29, 2014 12:41:29 PM UTC-5, Joel E wrote:
>
> I posted the details of this issue on StackOverflow here 
> 
>  
> but basically the Users API is crashing when accessed by an app running on 
> a custom domain. I have not been able to get any help with this issue and 
> it would be great to get an answer from someone at Google as this seems to 
> be an issue with App Engine's internal code. I'd be happy for any 
> suggestions or help at this point though.
>
> Thanks!
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Will cloud Dataflows replace the MapReduce/Pipeline API?

['Tom Kaitchuck' via Google App Engine]

Yes. Multiple namespaces are not directly supported. Given a finite known
set, the simplest thing to do would be to construct an InMemoryInput and
have the mapper operate on a namespace. You could also, for instance create
a new input class that iterated over namespaces.

Both of the above are predicated on the idea that the mapper can operate on
a namespace as a single item. If this is not practical, there is not much
that can be done. It is not possible to issue / shard a datastore query
that crosses namespaces. So there is no good way to shard the data.


On Tue, Jul 29, 2014 at 4:26 AM, Aswath Satrasala <
aswath.satras...@gmail.com> wrote:

> That is correct.  It support one namespace.  If there are 1000 namespaces,
> then we have to setup 1000 mapreduce jobs, and monitor them.
> It is more work and not convenient, if you are doing data processing more
> often.
> Please star this issue, if you are using namespace and mapreduce
> https://code.google.com/p/appengine-mapreduce/issues/detail?id=108
>
>
>
>
> On Fri, Jul 25, 2014 at 12:13 AM, 'Tom Kaitchuck' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> Mapreduce does support namespaces:
>>
>> https://code.google.com/p/appengine-mapreduce/source/browse/trunk/java/src/main/java/com/google/appengine/tools/mapreduce/inputs/DatastoreInput.java#28
>>
>>
>> On Thu, Jul 24, 2014 at 12:28 AM, Aswath Satrasala <
>> aswath.satras...@gmail.com> wrote:
>>
>>> Currently, mapreduce does not support namespaces well and takes takes
>>> longer time to setup and code.
>>> Any idea, on the the dataflow when it will be for public?  Will it
>>> support for processing namespaces data in appengine?
>>>
>>> -Aswath
>>>
>>>
>>>
>>> On Fri, Jun 27, 2014 at 12:18 AM, 'Tom Kaitchuck' via Google App Engine
>>>  wrote:
>>>
 No

 --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] 500 server error on App Engine when using OpenID Users API on custom domain

[Joel E]

I posted the details of this issue on StackOverflow here 

 
but basically the Users API is crashing when accessed by an app running on 
a custom domain. I have not been able to get any help with this issue and 
it would be great to get an answer from someone at Google as this seems to 
be an issue with App Engine's internal code. I'd be happy for any 
suggestions or help at this point though.

Thanks!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Datastore Indexes... What's actually supported... My understanding

[Kinesh Patel]

I don't have an answer or comment to your question, but please star the 
issue below :)

https://code.google.com/p/googleappengine/issues/detail?id=8305&q=indexes&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log



On Saturday, July 26, 2014 12:48:41 AM UTC-4, Doug Anderson wrote:
>
> Having recently significantly exceeded the 200 index limit... I began 
> trying to figure out what GAE actually supports in a desperate attempt to 
> get back under the limit.  You'd think the documentation would make this 
> clear and maybe it does for bigger brains than mine.  But for me some of 
> the older articles and videos just muddy the water and make it unclear 
> what's actually real today vs wishful thinking from the past.  The 2011 
> Alfred Fuller article does a pretty good job of getting you on the right 
> track (https://developers.google.com/appengine/articles/indexselection). 
>  The Zigzag merge join that Alfred describes seems to be real and available 
> today.  However, there is one limitation that was unclear to me and I 
> summarize my understanding as follows:
>
> *GAE can use any combination of indexes to satisfy a query AS LONG AS the 
> index contains no outsiders.*
>
> In other words... every field in an index MUST be in the filter expression 
> or the index will NOT be used!!!
>
> Stated yet another way... GAE does NOT use more specific indexes to 
> satisfy less specific queries.
>
> For example,
>
> Index(Model, field1, field2, fieldSort)
> Can NOT be used with:
>SELECT * from Model WHERE field1=val1 ORDER BY fieldSort
>SELECT * from Model WHERE field2=val2 ORDER BY fieldSort
> Because the index contains fields that are NOT in the filter expression of 
> each query
>
> Given,
>
> Index(Model, field1, field2, fieldSort)
> Index(Model, field3, field4, fieldSort)
> CAN be used with:
>SELECT * from Model WHERE field1=val1 AND field2=val2  ORDER BY 
> fieldSort
>SELECT * from Model WHERE field3=val3 AND field4=val4  ORDER BY 
> fieldSort
>SELECT * from Model WHERE field1=val1 AND field2=val2 AND field3=val3 
> AND field4=val4 ORDER BY fieldSort
> Can NOT be used with:
>SELECT * from Model WHERE field1=val1 AND field2=val2 AND field3=val3 
> ORDER BY fieldSort
>(or any other combination of 3 fields)
> BECAUSE the second index contains field4 (an outsider) which is NOT in the 
> filter expression!
> (and field3 isn't available in any other index)
>
> Indexing each field individually as Alfred discusses works for any 
> combination of fields 1-4 with fieldSort because GAE can
> always find a set of indexes that contain no outsiders.  It's really as 
> simple as that!
>
> Overlap is OK but outsiders are NOT
>
> Index(Model, field1, field2, field3, fieldSort)
> Index(Model, field2, field3, field4, fieldSort)
> CAN be used with:
>SELECT * from Model WHERE field1=val1 AND field2=val2 AND field3=val3 
> AND field4=val4 ORDER BY fieldSort
> The overlap of fields 2,3 in the indexes are OK and there are no outsiders 
> in either index
> However, now the following queries DON''T WORK because there are outsiders 
> in the available indexes:
>SELECT * from Model WHERE field1=val1 AND field2=val2  ORDER BY 
> fieldSort  (field3 is an outsider)
>SELECT * from Model WHERE field3=val3 AND field4=val4  ORDER BY 
> fieldSort  (field2 is an outsider)
>
> Anyway... I just thought I would share my insight FWIW
> I still don't know if I can make the 200 index limit but at least now *I 
> think* I understand what works and what doesn't. :)
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Will cloud Dataflows replace the MapReduce/Pipeline API?

[Aswath Satrasala]

That is correct.  It support one namespace.  If there are 1000 namespaces,
then we have to setup 1000 mapreduce jobs, and monitor them.
It is more work and not convenient, if you are doing data processing more
often.
Please star this issue, if you are using namespace and mapreduce
https://code.google.com/p/appengine-mapreduce/issues/detail?id=108




On Fri, Jul 25, 2014 at 12:13 AM, 'Tom Kaitchuck' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Mapreduce does support namespaces:
>
> https://code.google.com/p/appengine-mapreduce/source/browse/trunk/java/src/main/java/com/google/appengine/tools/mapreduce/inputs/DatastoreInput.java#28
>
>
> On Thu, Jul 24, 2014 at 12:28 AM, Aswath Satrasala <
> aswath.satras...@gmail.com> wrote:
>
>> Currently, mapreduce does not support namespaces well and takes takes
>> longer time to setup and code.
>> Any idea, on the the dataflow when it will be for public?  Will it
>> support for processing namespaces data in appengine?
>>
>> -Aswath
>>
>>
>>
>> On Fri, Jun 27, 2014 at 12:18 AM, 'Tom Kaitchuck' via Google App Engine <
>> google-appengine@googlegroups.com> wrote:
>>
>>> No
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.