[google-appengine] Inactive Instances

[PanosJee]

Hi everyone,
My app is currently using 8 instances. 3 of them have 0 QPS and they live 
for over 8 hours. Has the scheduler any issues and is not killing old 
instances? I am afraid it will take a toll on my app once the new pricing 
in enabled.

1.933126.9 ms17600:01:2638.3 MBytes[image: Dynamic Icon]Dynamic1.050124.8 ms
6200:00:2829.9 MBytes[image: Dynamic Icon]Dynamic0.533226.1 ms3100:00:2733.1 
MBytes[image: Dynamic Icon]Dynamic3.55085.6 ms82200:04:2839.1 MBytes[image: 
Dynamic Icon]Dynamic0..0 ms2608:31:1921.0 MBytes[image: Dynamic Icon]
Dynamic0..0 ms1407:16:5917.2 MBytes[image: Dynamic Icon]Dynamic0..0 
ms67
010:59:3129.6 MBytes[image: Dynamic Icon]Dynamic


Thanks

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

Re: [google-appengine] Re: URGENT: memcache errors out on write, the entire site is down

[Johan Euphrosine]

After taking a closer look at the implementation, I found the method
throwing the reported exception (MemcacheServiceException):
http://www.google.com/codesearch#Qx8E-7HUBTk/trunk/java/src/main/com/google/appengine/api/memcache/AsyncMemcacheServiceImpl.java&l=462

It appears that it doesn't rely on getErrorHandler for routing errors
and throws MemcacheServiceException directly.

That should be pretty easy to verify using an unittest.

Let me know if I missed something.

On Thu, Oct 27, 2011 at 2:19 PM, Johan Euphrosine  wrote:
> Jeff, you are right the default handler is supposed to handle both
> DeserializationError and ServiceError:
> http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/memcache/LogAndContinueErrorHandler.java
>
> Jon did you change the default memcache error handler ?
>
> On Thu, Oct 27, 2011 at 1:37 PM, Jeff Schnitzer  wrote:
>> Are you saying that we should not expect the
>> MemcacheService.set/getErrorHandler(), with its default value of
>> LogAndContinueErrorHandler, to do what it says?  I expect memcacheservice to
>> fail silently.
>> Is it possible that the error handler showed up in 1.5.5?  The OP mentioned
>> in another thread that he is running on 1.5.4.
>> Jeff
>> On Wed, Oct 26, 2011 at 5:12 PM, Johan Euphrosine  wrote:
>>>
>>> Hi Jon,
>>>
>>> It is important that you have proper exception handling for all your
>>> API calls, as there is always a possibility of them failing (otherwise
>>> we wouldn't document those methods as throwing an exception). In the
>>> catch block you should usually fallback or retry gracefully: for
>>> memcache it makes senses to fallback on datastore (more latency, but
>>> more reliable).
>>>
>>> In addition you can use the capabilities API to proactively query if a
>>> given API is available, this is described in details by Nick Johnson
>>> in the following blog  post:
>>>
>>> http://blog.notdot.net/2010/03/Handling-downtime-The-capabilities-API-and-testing
>>>
>>> Hope that helps.
>>>
>>> On Thu, Oct 27, 2011 at 8:28 AM, jon  wrote:
>>> > How did you fix/get around this problem?
>>> >
>>> > It was pointed out to me that the MemcacheService by default should
>>> > *NOT* throw any exception, therefore what I was seeing is a bug.
>>> >
>>> > Can anyone from Google confirm if this is the case? I'm using 1.5.4.
>>> >
>>> > On Oct 26, 9:32 am, James Broberg  wrote:
>>> >> Fair enough. At least you got a memcache exception :) In our case
>>> >> performance just deteriorated and eventually it timed out.
>>> >>
>>> >> On 26 October 2011 00:17, jon  wrote:
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> > Thanks James for pointing them out. They're not entirely identical in
>>> >> > that the symptom is different (i.e. the exception I got is
>>> >> > different).
>>> >> > However there's a common pattern whereby an app seems to be assigned
>>> >> > a
>>> >> > memcache "service provider" and if this provider misbehaves the app
>>> >> > will be stuck with it instead of getting reassigned a new, healthy
>>> >> > replacement.
>>> >>
>>> >> > On Oct 25, 11:26 pm, James Broberg  wrote:
>>> >> >> Sounds familiar:
>>> >>
>>> >>
>>> >> >> >>http://code.google.com/p/googleappengine/issues/detail?id=5790http://...
>>> >>
>>> >> >> On 25 October 2011 20:16, jon  wrote:
>>> >>
>>> >> >> > Memcache for our app is back now.
>>> >>
>>> >> >> > According to the log, memcache write operations started throwing
>>> >> >> > com.google.appengine.api.memcache.MemcacheServiceException at
>>> >> >> > 17:49
>>> >> >> > (Melbourne
>>> >> >> > time) and stopped at 18:56. In other words memcache was
>>> >> >> > unavailable
>>> >> >> > for over 1
>>> >> >> > hour.
>>> >>
>>> >> >> > We use memcache heavily, so our site would've been down for that
>>> >> >> > long
>>> >> >> > if we
>>> >> >> > hadn't stepped in to turn off all uses of memcache.
>>> >>
>>> >> >> > Question for Google: is there an affinity between an app and it's
>>> >> >> > memcache
>>> >> >> > service provider? How can memcache consistently error out for the
>>> >> >> > same
>>> >> >> > application for that long?
>>> >>
>>> >> >> > On Oct 25, 6:29 pm, jon  wrote:
>>> >> >> >> Hi,
>>> >>
>>> >> >> >> Writing to memcache is down for one of our apps, other apps are
>>> >> >> >> OK.
>>> >>
>>> >> >> >> The error message says:
>>> >> >> >> java.lang.RuntimeException:
>>> >> >> >> com.google.appengine.api.memcache.MemcacheServiceException:
>>> >> >> >> Memcache
>>> >> >> >> put: Set failed to set 20 keys
>>> >>
>>> >> >> >> The affected app id: thecrowdvoice
>>> >>
>>> >> >> >> Could someone from Google urgently take a look please?
>>> >>
>>> >> >> >> Thanks in advance,
>>> >> >> >> Jon
>>> >>
>>> >> >> > --
>>> >> >> > You received this message because you are subscribed to the Google
>>> >> >> > Groups "Google App Engine" group.
>>> >> >> > To post to this group, send email to
>>> >> >> > google-appengine@googlegroups.com.
>>> >> >> > To unsubscribe from this group, send e

Re: [google-appengine] Re: URGENT: memcache errors out on write, the entire site is down

[Johan Euphrosine]

Jeff, you are right the default handler is supposed to handle both
DeserializationError and ServiceError:
http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/memcache/LogAndContinueErrorHandler.java

Jon did you change the default memcache error handler ?

On Thu, Oct 27, 2011 at 1:37 PM, Jeff Schnitzer  wrote:
> Are you saying that we should not expect the
> MemcacheService.set/getErrorHandler(), with its default value of
> LogAndContinueErrorHandler, to do what it says?  I expect memcacheservice to
> fail silently.
> Is it possible that the error handler showed up in 1.5.5?  The OP mentioned
> in another thread that he is running on 1.5.4.
> Jeff
> On Wed, Oct 26, 2011 at 5:12 PM, Johan Euphrosine  wrote:
>>
>> Hi Jon,
>>
>> It is important that you have proper exception handling for all your
>> API calls, as there is always a possibility of them failing (otherwise
>> we wouldn't document those methods as throwing an exception). In the
>> catch block you should usually fallback or retry gracefully: for
>> memcache it makes senses to fallback on datastore (more latency, but
>> more reliable).
>>
>> In addition you can use the capabilities API to proactively query if a
>> given API is available, this is described in details by Nick Johnson
>> in the following blog  post:
>>
>> http://blog.notdot.net/2010/03/Handling-downtime-The-capabilities-API-and-testing
>>
>> Hope that helps.
>>
>> On Thu, Oct 27, 2011 at 8:28 AM, jon  wrote:
>> > How did you fix/get around this problem?
>> >
>> > It was pointed out to me that the MemcacheService by default should
>> > *NOT* throw any exception, therefore what I was seeing is a bug.
>> >
>> > Can anyone from Google confirm if this is the case? I'm using 1.5.4.
>> >
>> > On Oct 26, 9:32 am, James Broberg  wrote:
>> >> Fair enough. At least you got a memcache exception :) In our case
>> >> performance just deteriorated and eventually it timed out.
>> >>
>> >> On 26 October 2011 00:17, jon  wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> > Thanks James for pointing them out. They're not entirely identical in
>> >> > that the symptom is different (i.e. the exception I got is
>> >> > different).
>> >> > However there's a common pattern whereby an app seems to be assigned
>> >> > a
>> >> > memcache "service provider" and if this provider misbehaves the app
>> >> > will be stuck with it instead of getting reassigned a new, healthy
>> >> > replacement.
>> >>
>> >> > On Oct 25, 11:26 pm, James Broberg  wrote:
>> >> >> Sounds familiar:
>> >>
>> >>
>> >> >> >>http://code.google.com/p/googleappengine/issues/detail?id=5790http://...
>> >>
>> >> >> On 25 October 2011 20:16, jon  wrote:
>> >>
>> >> >> > Memcache for our app is back now.
>> >>
>> >> >> > According to the log, memcache write operations started throwing
>> >> >> > com.google.appengine.api.memcache.MemcacheServiceException at
>> >> >> > 17:49
>> >> >> > (Melbourne
>> >> >> > time) and stopped at 18:56. In other words memcache was
>> >> >> > unavailable
>> >> >> > for over 1
>> >> >> > hour.
>> >>
>> >> >> > We use memcache heavily, so our site would've been down for that
>> >> >> > long
>> >> >> > if we
>> >> >> > hadn't stepped in to turn off all uses of memcache.
>> >>
>> >> >> > Question for Google: is there an affinity between an app and it's
>> >> >> > memcache
>> >> >> > service provider? How can memcache consistently error out for the
>> >> >> > same
>> >> >> > application for that long?
>> >>
>> >> >> > On Oct 25, 6:29 pm, jon  wrote:
>> >> >> >> Hi,
>> >>
>> >> >> >> Writing to memcache is down for one of our apps, other apps are
>> >> >> >> OK.
>> >>
>> >> >> >> The error message says:
>> >> >> >> java.lang.RuntimeException:
>> >> >> >> com.google.appengine.api.memcache.MemcacheServiceException:
>> >> >> >> Memcache
>> >> >> >> put: Set failed to set 20 keys
>> >>
>> >> >> >> The affected app id: thecrowdvoice
>> >>
>> >> >> >> Could someone from Google urgently take a look please?
>> >>
>> >> >> >> Thanks in advance,
>> >> >> >> Jon
>> >>
>> >> >> > --
>> >> >> > You received this message because you are subscribed to the Google
>> >> >> > Groups "Google App Engine" group.
>> >> >> > To post to this group, send email to
>> >> >> > google-appengine@googlegroups.com.
>> >> >> > To unsubscribe from this group, send email to
>> >> >> > google-appengine+unsubscr...@googlegroups.com.
>> >> >> > For more options, visit this group
>> >> >> > athttp://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-appengine@googlegroups.com.
>> >> > To unsubscribe from this group, send email to
>> >> > google-appengine+unsubscr...@googlegroups.com.
>> >> > For more options, visit this group
>> >> > athttp://groups.google.com/group/google-appengine?hl=en.
>> >
>> > --
>> > You received this 

Re: [google-appengine] Re: URGENT: memcache errors out on write, the entire site is down

[Jeff Schnitzer]

Are you saying that we should not expect the
MemcacheService.set/getErrorHandler(), with its default value of
LogAndContinueErrorHandler, to do what it says?  I expect memcacheservice to
fail silently.

Is it possible that the error handler showed up in 1.5.5?  The OP mentioned
in another thread that he is running on 1.5.4.

Jeff

On Wed, Oct 26, 2011 at 5:12 PM, Johan Euphrosine  wrote:

> Hi Jon,
>
> It is important that you have proper exception handling for all your
> API calls, as there is always a possibility of them failing (otherwise
> we wouldn't document those methods as throwing an exception). In the
> catch block you should usually fallback or retry gracefully: for
> memcache it makes senses to fallback on datastore (more latency, but
> more reliable).
>
> In addition you can use the capabilities API to proactively query if a
> given API is available, this is described in details by Nick Johnson
> in the following blog  post:
>
> http://blog.notdot.net/2010/03/Handling-downtime-The-capabilities-API-and-testing
>
> Hope that helps.
>
> On Thu, Oct 27, 2011 at 8:28 AM, jon  wrote:
> > How did you fix/get around this problem?
> >
> > It was pointed out to me that the MemcacheService by default should
> > *NOT* throw any exception, therefore what I was seeing is a bug.
> >
> > Can anyone from Google confirm if this is the case? I'm using 1.5.4.
> >
> > On Oct 26, 9:32 am, James Broberg  wrote:
> >> Fair enough. At least you got a memcache exception :) In our case
> >> performance just deteriorated and eventually it timed out.
> >>
> >> On 26 October 2011 00:17, jon  wrote:
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> > Thanks James for pointing them out. They're not entirely identical in
> >> > that the symptom is different (i.e. the exception I got is different).
> >> > However there's a common pattern whereby an app seems to be assigned a
> >> > memcache "service provider" and if this provider misbehaves the app
> >> > will be stuck with it instead of getting reassigned a new, healthy
> >> > replacement.
> >>
> >> > On Oct 25, 11:26 pm, James Broberg  wrote:
> >> >> Sounds familiar:
> >>
> >> >>
> http://code.google.com/p/googleappengine/issues/detail?id=5790http://...
> >>
> >> >> On 25 October 2011 20:16, jon  wrote:
> >>
> >> >> > Memcache for our app is back now.
> >>
> >> >> > According to the log, memcache write operations started throwing
> >> >> > com.google.appengine.api.memcache.MemcacheServiceException at 17:49
> >> >> > (Melbourne
> >> >> > time) and stopped at 18:56. In other words memcache was unavailable
> >> >> > for over 1
> >> >> > hour.
> >>
> >> >> > We use memcache heavily, so our site would've been down for that
> long
> >> >> > if we
> >> >> > hadn't stepped in to turn off all uses of memcache.
> >>
> >> >> > Question for Google: is there an affinity between an app and it's
> >> >> > memcache
> >> >> > service provider? How can memcache consistently error out for the
> same
> >> >> > application for that long?
> >>
> >> >> > On Oct 25, 6:29 pm, jon  wrote:
> >> >> >> Hi,
> >>
> >> >> >> Writing to memcache is down for one of our apps, other apps are
> OK.
> >>
> >> >> >> The error message says:
> >> >> >> java.lang.RuntimeException:
> >> >> >> com.google.appengine.api.memcache.MemcacheServiceException:
> Memcache
> >> >> >> put: Set failed to set 20 keys
> >>
> >> >> >> The affected app id: thecrowdvoice
> >>
> >> >> >> Could someone from Google urgently take a look please?
> >>
> >> >> >> Thanks in advance,
> >> >> >> Jon
> >>
> >> >> > --
> >> >> > You received this message because you are subscribed to the Google
> Groups "Google App Engine" group.
> >> >> > To post to this group, send email to
> google-appengine@googlegroups.com.
> >> >> > To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> >> >> > For more options, visit this group athttp://
> 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-appengine@googlegroups.com.
> >> > To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> >> > For more options, visit this group athttp://
> 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-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
> >
> >
>
>
>
> --
> Johan Euphrosine (proppy)
> Developer Programs Engineer
> Google Developer Relations
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to 

RE: [google-appengine] Re: The Dining Philosophers

[Brandon Wirtz]

My first time interviewing at Microsoft I got the Philosophers question with
Rice and Chopsticks.  I proposed two solutions... 

One that worked on position and timing... 

The other was the "Python 2.7" fix. 

doonce(BreakChopSticks);

do{think;}
while(hungry!=true)

Cut the chopsticks in half and let everyone eat half as fast, but think on
their own schedule.   The philosophers will be happier, and the code is
easier to write.



-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Emlyn
Sent: Wednesday, October 26, 2011 5:39 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] Re: The Dining Philosophers

On 25 October 2011 02:18, Kyle  wrote:
> Is there a reason that you didn't use the memcached service to 
> implement semaphores?
>
> -Kyle

I'm assuming you mean Memcache?

Well, two things. Firstly, as far as I know there are no transactions or
locks or anything like that for memcache, so where you need a critical
section, how will you implement it? (This is not actually a rhetorical
question; is there a way?)

Secondly, you can't trust Memcache to stick around, as far as I know.
If one task constructs a semaphore in memcache, then will that still be
there when another tasks tries to wait() on it?

Anything that is implemented in terms of Semaphores really needs to be able
to rely on them to behave. It might be good to come up with an alternative
construct that can tolerate memcache's behaviour, I'm totally open to
suggestions.



>
> On Oct 23, 6:23 am, Emlyn  wrote:
>> Here's a new AppEngine article from me, "The Dining Philosophers". It 
>> includes a full working implementation of Semaphores using the 
>> Datastore, and implementation of flawed and successful solutions to 
>> the classic Dining Philosophers problem using Semaphores.
>>
>> http://appenginedevelopment.blogspot.com/2011/10/dining-philosophers
>>
>> Fun for hard core comp sci types ;-)
>>
>> --
>> Emlyn
>>
>> http://my.syyn.cc- Synchonise Google+, Facebook, WordPress and Google 
>> Buzz posts, comments and all.http://point7.wordpress.com- My blog 
>> Find me on Facebook and Buzz
>
> --
> You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
>
>



--
Emlyn

http://my.syyn.cc - Synchonise Google+, Facebook, WordPress and Google Buzz
posts, comments and all.
http://point7.wordpress.com - My blog
Find me on Facebook and Buzz

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


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

Re: [google-appengine] deployement to google failed

[Amy Unruh]

Abderrahim,

>From the message, it looks like there is a problem with the app.yaml file
for your project. See
http://code.google.com/appengine/docs/python/config/appconfig.html for more
information about application configuration.
You could try comparing your file to the app.yaml in a working sample app,
or list it here if you are still stumped.

 -Amy

On Mon, Oct 24, 2011 at 10:39 PM, Abderrahim AGDICHE wrote:

> Hello!
> When i try de debloy ma webDb to google i receive this:
> --
> 2011-10-24 11:32:20 Running command: "['C:\\Python25\\pythonw.exe', '-
> u', 'C:\\Program Files\\Google\\google_appengine\\appcfg.py', '--
> no_cookies', u'--email=a.agdi...@gmail.com', '--passin', 'update', 'D:\
> \customtinywebdb\\customtinywebdb']"
> Error parsing yaml file:
> mapping values are not allowed here
>  in "D:\customtinywebdb\customtinywebdb\app.yaml", line 1, column 22
> 2011-10-24 11:32:22 (Process exited with code 1)
>
> You can close this window now.
> --
>
> Can some body help me to resolve this, also there is no sample datas
> in "customtinywebdb" ??
>
> Thank you.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

[google-appengine] Re: Emails sent from GAE apps to yahoo or hotmail addresses get tagged as spam

[Greg]

On Oct 27, 12:45 am, Joshua Smith  wrote:
> mailto:regis...@myapp.appspotmail.com?subject=a9b8c7d6e5f

How bulletproof is the subject in a mailto: URL? I tried it years ago,
and many email clients ignored it completely.

I'm about to move to SMS verification because if Google does it, it's
likely the best solution.

Cheers
Greg.

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

Re: [google-appengine] Re: The Dining Philosophers

[Emlyn]

On 25 October 2011 02:18, Kyle  wrote:
> Is there a reason that you didn't use the memcached service to
> implement semaphores?
>
> -Kyle

I'm assuming you mean Memcache?

Well, two things. Firstly, as far as I know there are no transactions
or locks or anything like that for memcache, so where you need a
critical section, how will you implement it? (This is not actually a
rhetorical question; is there a way?)

Secondly, you can't trust Memcache to stick around, as far as I know.
If one task constructs a semaphore in memcache, then will that still
be there when another tasks tries to wait() on it?

Anything that is implemented in terms of Semaphores really needs to be
able to rely on them to behave. It might be good to come up with an
alternative construct that can tolerate memcache's behaviour, I'm
totally open to suggestions.



>
> On Oct 23, 6:23 am, Emlyn  wrote:
>> Here's a new AppEngine article from me, "The Dining Philosophers". It
>> includes a full working implementation of Semaphores using the
>> Datastore, and implementation of flawed and successful solutions to
>> the classic Dining Philosophers problem using Semaphores.
>>
>> http://appenginedevelopment.blogspot.com/2011/10/dining-philosophers
>>
>> Fun for hard core comp sci types ;-)
>>
>> --
>> Emlyn
>>
>> http://my.syyn.cc- Synchonise Google+, Facebook, WordPress and Google
>> Buzz posts,
>> comments and all.http://point7.wordpress.com- My blog
>> Find me on Facebook and Buzz
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>



-- 
Emlyn

http://my.syyn.cc - Synchonise Google+, Facebook, WordPress and Google
Buzz posts,
comments and all.
http://point7.wordpress.com - My blog
Find me on Facebook and Buzz

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

Re: [google-appengine] Re: URGENT: memcache errors out on write, the entire site is down

[Johan Euphrosine]

Hi Jon,

It is important that you have proper exception handling for all your
API calls, as there is always a possibility of them failing (otherwise
we wouldn't document those methods as throwing an exception). In the
catch block you should usually fallback or retry gracefully: for
memcache it makes senses to fallback on datastore (more latency, but
more reliable).

In addition you can use the capabilities API to proactively query if a
given API is available, this is described in details by Nick Johnson
in the following blog  post:
http://blog.notdot.net/2010/03/Handling-downtime-The-capabilities-API-and-testing

Hope that helps.

On Thu, Oct 27, 2011 at 8:28 AM, jon  wrote:
> How did you fix/get around this problem?
>
> It was pointed out to me that the MemcacheService by default should
> *NOT* throw any exception, therefore what I was seeing is a bug.
>
> Can anyone from Google confirm if this is the case? I'm using 1.5.4.
>
> On Oct 26, 9:32 am, James Broberg  wrote:
>> Fair enough. At least you got a memcache exception :) In our case
>> performance just deteriorated and eventually it timed out.
>>
>> On 26 October 2011 00:17, jon  wrote:
>>
>>
>>
>>
>>
>>
>>
>> > Thanks James for pointing them out. They're not entirely identical in
>> > that the symptom is different (i.e. the exception I got is different).
>> > However there's a common pattern whereby an app seems to be assigned a
>> > memcache "service provider" and if this provider misbehaves the app
>> > will be stuck with it instead of getting reassigned a new, healthy
>> > replacement.
>>
>> > On Oct 25, 11:26 pm, James Broberg  wrote:
>> >> Sounds familiar:
>>
>> >>http://code.google.com/p/googleappengine/issues/detail?id=5790http://...
>>
>> >> On 25 October 2011 20:16, jon  wrote:
>>
>> >> > Memcache for our app is back now.
>>
>> >> > According to the log, memcache write operations started throwing
>> >> > com.google.appengine.api.memcache.MemcacheServiceException at 17:49
>> >> > (Melbourne
>> >> > time) and stopped at 18:56. In other words memcache was unavailable
>> >> > for over 1
>> >> > hour.
>>
>> >> > We use memcache heavily, so our site would've been down for that long
>> >> > if we
>> >> > hadn't stepped in to turn off all uses of memcache.
>>
>> >> > Question for Google: is there an affinity between an app and it's
>> >> > memcache
>> >> > service provider? How can memcache consistently error out for the same
>> >> > application for that long?
>>
>> >> > On Oct 25, 6:29 pm, jon  wrote:
>> >> >> Hi,
>>
>> >> >> Writing to memcache is down for one of our apps, other apps are OK.
>>
>> >> >> The error message says:
>> >> >> java.lang.RuntimeException:
>> >> >> com.google.appengine.api.memcache.MemcacheServiceException: Memcache
>> >> >> put: Set failed to set 20 keys
>>
>> >> >> The affected app id: thecrowdvoice
>>
>> >> >> Could someone from Google urgently take a look please?
>>
>> >> >> Thanks in advance,
>> >> >> Jon
>>
>> >> > --
>> >> > You received this message because you are subscribed to the Google 
>> >> > Groups "Google App Engine" group.
>> >> > To post to this group, send email to google-appengine@googlegroups.com.
>> >> > To unsubscribe from this group, send email to 
>> >> > google-appengine+unsubscr...@googlegroups.com.
>> >> > For more options, visit this group 
>> >> > athttp://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-appengine@googlegroups.com.
>> > To unsubscribe from this group, send email to 
>> > google-appengine+unsubscr...@googlegroups.com.
>> > For more options, visit this group 
>> > athttp://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-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

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

[google-appengine] Re: Emails sent from GAE apps to yahoo or hotmail addresses get tagged as spam

[jon]

Brandon would you mind sharing the link to this whitelisting facility?

I Googled it, only found instructions for client side whitelisting.

Thanks in advance.

On Oct 27, 8:36 am, "Brandon Wirtz"  wrote:
> Fill out the paperwork, and attend the seminar on LiveMail White Listing.
> Takes about 12 hours and then your domain is white listed on Hotmail, Live
> Mail, and Yahoo Mail.  The cost is something like $200 and well worth it.
> They do the seminars 4 times a year.
>
>
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
>
> [mailto:google-appengine@googlegroups.com] On Behalf Of Kaan Soral
> Sent: Wednesday, October 26, 2011 12:09 PM
> To: Google App Engine
> Subject: [google-appengine] Re: Emails sent from GAE apps to yahoo or
> hotmail addresses get tagged as spam
>
> Nope, you shouldn't make users think, a lot of them will just get confused
>
> On Oct 26, 2:45 pm, Joshua Smith  wrote:
> > Perhaps we're all pushing the rock uphill when we really should be letting
> it roll downhill:
>
> > Anyone ever try doing a user registration like this:
>
> > - Generate a mailto URL with the app as the addressee, and the subject set
> to a token:
>
> > mailto:regis...@myapp.appspotmail.com?subject=a9b8c7d6e5f
>
> > - The user clicks that link, and sends the message
>
> > - Using polling or a channel the page waits for appengine to get their
> > email
>
> > - When the server gets the mail, you create the registered account
>
> > - Remind the user what email address they should use to log in, since
> > you know it from their email, and they might not be too clear on what
> > their email address really is (a frighteningly common occurrence, I've
> > noticed)
>
> > Thoughts?
>
> > On Oct 26, 2011, at 1:25 AM, Tapir wrote:
>
> > > Yes, my app has been experiencing this problem for a long time.
> > > Half of my app new users will not activate their accounts.
> > > I found some of them try to register a new account with the last
> > > just created account inactivated.
> > > So I guess they haven't received the activation mails.
>
> > > I haven't got a efficient way to fix this problem.
> > > The problem is I don't know whether of not the new users have
> > > received the activation mails.
> > > There is no way to determine whether the activation mails are sent
> > > successfully or not.
>
> > > I have put a obvious notification at the top of each page for
> > > inactivated users.
> > > But the rate of activated accounts is still not increased.
>
> > > On Oct 25, 8:48 am, Rishi Arora  wrote:
> > >> I have only see this thread on the
> subject:http://groups.google.com/group/google-appengine/browse_thread/thread/...
> > >> And the resolution was to move to Amazon SES or other 3rd party
> > >> email service providers.
>
> > >> Anyone experienced this lately, and have any suggestions on how to
> > >> avoid being marked as spam?  The emails I generate are mostly "email
> confirmation"
> > >> type emails, where I generate a 64-byte random string to be used in
> > >> URL that the recipient clicks on to confirm that they are the owner
> > >> of the said email account.  The email, in my case, originates from
> > >> u...@appi-id.appspotmail.com, and I'm setting the reply-to field to
> > >> my google apps domain, which is obviously different from the GAE app
> domain.
> > >>  Perhaps I should not override the "reply-to" field in the header
> > >> of the emails I send.  This might be somewhat of an inconvenience in
> some cases.
>
> > >> Thanks in advance.
>
> > > --
> > > You received this message because you are subscribed to the Google
> Groups "Google App Engine" group.
> > > To post to this group, send email to google-appengine@googlegroups.com.
> > > To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group
> athttp://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-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group 
> athttp://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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: URGENT: memcache errors out on write, the entire site is down

[jon]

How did you fix/get around this problem?

It was pointed out to me that the MemcacheService by default should
*NOT* throw any exception, therefore what I was seeing is a bug.

Can anyone from Google confirm if this is the case? I'm using 1.5.4.

On Oct 26, 9:32 am, James Broberg  wrote:
> Fair enough. At least you got a memcache exception :) In our case
> performance just deteriorated and eventually it timed out.
>
> On 26 October 2011 00:17, jon  wrote:
>
>
>
>
>
>
>
> > Thanks James for pointing them out. They're not entirely identical in
> > that the symptom is different (i.e. the exception I got is different).
> > However there's a common pattern whereby an app seems to be assigned a
> > memcache "service provider" and if this provider misbehaves the app
> > will be stuck with it instead of getting reassigned a new, healthy
> > replacement.
>
> > On Oct 25, 11:26 pm, James Broberg  wrote:
> >> Sounds familiar:
>
> >>http://code.google.com/p/googleappengine/issues/detail?id=5790http://...
>
> >> On 25 October 2011 20:16, jon  wrote:
>
> >> > Memcache for our app is back now.
>
> >> > According to the log, memcache write operations started throwing
> >> > com.google.appengine.api.memcache.MemcacheServiceException at 17:49
> >> > (Melbourne
> >> > time) and stopped at 18:56. In other words memcache was unavailable
> >> > for over 1
> >> > hour.
>
> >> > We use memcache heavily, so our site would've been down for that long
> >> > if we
> >> > hadn't stepped in to turn off all uses of memcache.
>
> >> > Question for Google: is there an affinity between an app and it's
> >> > memcache
> >> > service provider? How can memcache consistently error out for the same
> >> > application for that long?
>
> >> > On Oct 25, 6:29 pm, jon  wrote:
> >> >> Hi,
>
> >> >> Writing to memcache is down for one of our apps, other apps are OK.
>
> >> >> The error message says:
> >> >> java.lang.RuntimeException:
> >> >> com.google.appengine.api.memcache.MemcacheServiceException: Memcache
> >> >> put: Set failed to set 20 keys
>
> >> >> The affected app id: thecrowdvoice
>
> >> >> Could someone from Google urgently take a look please?
>
> >> >> Thanks in advance,
> >> >> Jon
>
> >> > --
> >> > You received this message because you are subscribed to the Google 
> >> > Groups "Google App Engine" group.
> >> > To post to this group, send email to google-appengine@googlegroups.com.
> >> > To unsubscribe from this group, send email to 
> >> > google-appengine+unsubscr...@googlegroups.com.
> >> > For more options, visit this group 
> >> > athttp://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-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Problem with app.yaml include "reportlab" : No module name

[Amy Unruh]

Emad,

In general, to use a module, you can copy it into your project directory.
 However, you don't need an app.yaml entry for it.  It looks like you are
defining the module directory as a static directory-- this is incorrect.

[Also, note that GAE does not support writing to the file system (see the
'Sandbox' section here:
http://code.google.com/appengine/docs/whatisgoogleappengine.html), so if
reportlab wants to create files, it will not be compatible].


On Tue, Oct 25, 2011 at 11:36 PM, Emad Maleki  wrote:

> Hi Everybody
> I have sever problem with GAE, I am pretty new in this stuff but i
> frastrated googling about 3 days to find proper answer.
> here is the challenge
> I have installed reportlab to produce PDF files. but i dont know how
> to fix the path, library and app.yaml things in order no to have  'exceptions.ImportError'>: No module named reportlab.lib.pagesizes
> error:
>
> Please someone simply describe what should some one do , when he wants
> to use external library in GOOGLE APP ENgine
>
> here is my app.yaml file
>
> application: pdft
> version: 1
> runtime: python
> api_version: 1
>
> handlers:
> - url: /favicon.ico
>  static_files: static/shared/favicon.ico
>  upload: static/shared/favicon.ico
>
> - url: /reportlab
>  static_dir: reportlab
>
> - url: /.*
>  script: test.py
>
> here is my code
>
> from reportlab.lib.pagesizes import A4
> from reportlab.pdfgen import canvas
>
> .
>
>
> Thank you in advanced,
> Emad
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

Re: [google-appengine] URLFetch is timing out excessively

[Nischal Shetty]

Yeah, you are right about that. I had faced it a few months ago following
which I moved that part to AWS. The other API calls though in excess are
below those variable limits.

I got a reply by twitter on their discussion forum that they are looking
into the issue. Hoping they find the cause soon.

On 26 October 2011 20:01, Brandon Wirtz  wrote:

> Signed calls are still subject to a variable rate limit based on Twitters
> given load. They throttle up and down based on available capacity.
>
> ** **
>
> ** **
>
> *From:* google-appengine@googlegroups.com [mailto:
> google-appengine@googlegroups.com] *On Behalf Of *Nischal Shetty
> *Sent:* Wednesday, October 26, 2011 2:47 PM
>
> *To:* google-appengine@googlegroups.com
> *Subject:* Re: [google-appengine] URLFetch is timing out excessively
>
> ** **
>
> It works from a non google environment. We have a service running on AWS
> which is working smooth. It's not a whitelist problem because these are
> signed calls which do not account for rate limiting based on IP.
>
> ** **
>
> Someone from google has replied saying the problem is not on their end. I
> have raised an issue on the twitter discussion forum (stupid of me to not
> have done that simultaneously). 
>
> ** **
>
> ** **
>
> On 26 October 2011 18:33, Brandon Wirtz  wrote:
>
> So you think that Fetches to only Twitter and FB are broken?   Did you try
> from a non-Goog Environment?  There are Fail Whales all over today.   
>
>  
>
> And if you are running “Hundreds of API calls a minute” you are likely
> hitting the API IP Limits since Twitter won’t grant a white list for Google
> IP’s.
>
>  
>
> You should be using a proxy to access twitter through a single IP what is
> on the Twitter API white List.
>
>  
>
>  
>
> *From:* google-appengine@googlegroups.com [mailto:
> google-appengine@googlegroups.com] *On Behalf Of *nischalshetty
> *Sent:* Wednesday, October 26, 2011 12:11 PM
> *To:* google-appengine@googlegroups.com
> *Subject:* Re: [google-appengine] URLFetch is timing out excessively
>
>  
>
> I agree twitter times out but this is not because of them. I'm talking
> about hundreds of timeout every minute.
>
>  
>
> We have things in place to retry timeouts, but I'm talkin about timeouts
> even after 3 retries with a timeout of 20 second each. 
>
>  
>
>  
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
>
> 
>
> ** **
>
> --
> -Nischal
>
> twitter: NischalShetty 
>
> facebook: Nischal 
>
> ** **
>
> [image: Description: Image removed by sender.]
>   [image: Description: Image removed by sender.] **
> **
>
> ** **
>
> ** **
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
-Nischal
twitter: NischalShetty 
facebook: Nischal 

 

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

<><>

RE: [google-appengine] Server Errors - Timeouts. Free accounts getting inferior service?

[Brandon Wirtz]

If you get 12 requests in 1 second, you now only have 1 instance, the free
service used to spin up additional instances and you were billed for CPU
time. As a result you used to be able to have 12 instances actually only
bill for 1 instance worth of CPU a day, (if they were waiting for things to
happen for example)

 

Likely you have users hitting your app, asking for 8 things at once, and
when you get 3 people at the same time, your instance can't serve all of
them before they time out.

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of David Manns
Sent: Monday, October 24, 2011 7:20 AM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Server Errors - Timeouts. Free accounts getting
inferior service?

 

This morning (and many times over recent weeks) my application, which
normally runs perfectly, encounters both very slow response times as well as
these server errors.  When I look at the logs, the errors are timeouts.  The
application uses the web2py framework.  The problem occurs both on the
initial screen either a login screen or a search form, depending on whether
a persistent login has been used - in either case no datastore access, and
at random times during a sequence of searches and edits of the database.

 

Perhaps related to business hours, often works more consistently off peak
hours.  Are free applications now being discriminated against and being
relegated to a small group of, at times, overloaded servers?

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

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

RE: [google-appengine] URLFetch is timing out excessively

[Brandon Wirtz]

Signed calls are still subject to a variable rate limit based on Twitters
given load. They throttle up and down based on available capacity.

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Nischal Shetty
Sent: Wednesday, October 26, 2011 2:47 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] URLFetch is timing out excessively

 

It works from a non google environment. We have a service running on AWS
which is working smooth. It's not a whitelist problem because these are
signed calls which do not account for rate limiting based on IP.

 

Someone from google has replied saying the problem is not on their end. I
have raised an issue on the twitter discussion forum (stupid of me to not
have done that simultaneously). 

 

 

On 26 October 2011 18:33, Brandon Wirtz  wrote:

So you think that Fetches to only Twitter and FB are broken?   Did you try
from a non-Goog Environment?  There are Fail Whales all over today.   

 

And if you are running "Hundreds of API calls a minute" you are likely
hitting the API IP Limits since Twitter won't grant a white list for Google
IP's.

 

You should be using a proxy to access twitter through a single IP what is on
the Twitter API white List.

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of nischalshetty
Sent: Wednesday, October 26, 2011 12:11 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] URLFetch is timing out excessively

 

I agree twitter times out but this is not because of them. I'm talking about
hundreds of timeout every minute.

 

We have things in place to retry timeouts, but I'm talkin about timeouts
even after 3 retries with a timeout of 20 second each. 

 

 

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

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





 

-- 
-Nischal

twitter: NischalShetty  

facebook: Nischal  

 

  Description: Image removed by sender.
 Description: Image removed by sender.

 

 

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

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

<><>

Re: [google-appengine] Re: URLFetch is timing out excessively

[Jeff Schnitzer]

You mean, the only site on the internet less reliable than twitter?

Jeff
(sorry - I don't have anything constructive to add, but I couldn't help
myself)

On Wed, Oct 26, 2011 at 12:20 PM, Vivek Puri  wrote:

> +1 . Requests to Facebook are also timing out.
>
>
> On Oct 26, 3:10 pm, nischalshetty  wrote:
> > I agree twitter times out but this is not because of them. I'm talking
> > about hundreds of timeout every minute.
> >
> > We have things in place to retry timeouts, but I'm talkin about timeouts
> > even after 3 retries with a timeout of 20 second each.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

Re: [google-appengine] Re: URLFetch is timing out excessively

[Nischal Shetty]

I saw the issue that you've reported on twitter. I've subscribed to that.
The issue that I reported on twitter has not been approved yet (probably
because ur issue is already visible) though @episod from twitter commented
that they are looking into the connectivity issue.

On 26 October 2011 18:56, Vivek Puri  wrote:

> Nischal,
>
> Send me link to the issue you report on Twitter. Thank you
>
>
>
> On Oct 26, 5:46 pm, Nischal Shetty  wrote:
> > It works from a non google environment. We have a service running on AWS
> > which is working smooth. It's not a whitelist problem because these are
> > signed calls which do not account for rate limiting based on IP.
> >
> > Someone from google has replied saying the problem is not on their end. I
> > have raised an issue on the twitter discussion forum (stupid of me to not
> > have done that simultaneously).
> >
> > On 26 October 2011 18:33, Brandon Wirtz  wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > So you think that Fetches to only Twitter and FB are broken?   Did you
> try
> > > from a non-Goog Environment?  There are Fail Whales all over today.
> 
> >
> > > ** **
> >
> > > And if you are running “Hundreds of API calls a minute” you are likely
> > > hitting the API IP Limits since Twitter won’t grant a white list for
> Google
> > > IP’s.
> >
> > > ** **
> >
> > > You should be using a proxy to access twitter through a single IP what
> is
> > > on the Twitter API white List.
> >
> > > ** **
> >
> > > ** **
> >
> > > *From:* google-appengine@googlegroups.com [mailto:
> > > google-appengine@googlegroups.com] *On Behalf Of *nischalshetty
> > > *Sent:* Wednesday, October 26, 2011 12:11 PM
> > > *To:* google-appengine@googlegroups.com
> > > *Subject:* Re: [google-appengine] URLFetch is timing out
> excessively
> >
> > > ** **
> >
> > > I agree twitter times out but this is not because of them. I'm talking
> > > about hundreds of timeout every minute.
> >
> > > ** **
> >
> > > We have things in place to retry timeouts, but I'm talkin about
> timeouts
> > > even after 3 retries with a timeout of 20 second each. 
> >
> > > ** **
> >
> > > ** **
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine" group.
> > > To view this discussion on the web visit
> > >https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.
> > > To post to this group, send email to google-appengine@googlegroups.com
> .
> > > To unsubscribe from this group, send email to
> > > google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine" group.
> > > To post to this group, send email to google-appengine@googlegroups.com
> .
> > > To unsubscribe from this group, send email to
> > > google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > -Nischal
> > twitter: NischalShetty 
> > facebook: Nischal 
> >
> >  
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
-Nischal
twitter: NischalShetty 
facebook: Nischal 

 

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

[google-appengine] Re: URLFetch is timing out excessively

[Vivek Puri]

Nischal,

Send me link to the issue you report on Twitter. Thank you



On Oct 26, 5:46 pm, Nischal Shetty  wrote:
> It works from a non google environment. We have a service running on AWS
> which is working smooth. It's not a whitelist problem because these are
> signed calls which do not account for rate limiting based on IP.
>
> Someone from google has replied saying the problem is not on their end. I
> have raised an issue on the twitter discussion forum (stupid of me to not
> have done that simultaneously).
>
> On 26 October 2011 18:33, Brandon Wirtz  wrote:
>
>
>
>
>
>
>
>
>
> > So you think that Fetches to only Twitter and FB are broken?   Did you try
> > from a non-Goog Environment?  There are Fail Whales all over today.   
>
> > ** **
>
> > And if you are running “Hundreds of API calls a minute” you are likely
> > hitting the API IP Limits since Twitter won’t grant a white list for Google
> > IP’s.
>
> > ** **
>
> > You should be using a proxy to access twitter through a single IP what is
> > on the Twitter API white List.
>
> > ** **
>
> > ** **
>
> > *From:* google-appengine@googlegroups.com [mailto:
> > google-appengine@googlegroups.com] *On Behalf Of *nischalshetty
> > *Sent:* Wednesday, October 26, 2011 12:11 PM
> > *To:* google-appengine@googlegroups.com
> > *Subject:* Re: [google-appengine] URLFetch is timing out excessively
>
> > ** **
>
> > I agree twitter times out but this is not because of them. I'm talking
> > about hundreds of timeout every minute.
>
> > ** **
>
> > We have things in place to retry timeouts, but I'm talkin about timeouts
> > even after 3 retries with a timeout of 20 second each. 
>
> > ** **
>
> > ** **
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To view this discussion on the web visit
> >https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> -Nischal
> twitter: NischalShetty 
> facebook: Nischal 
>
>      

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

Re: [google-appengine] URLFetch is timing out excessively

[Nischal Shetty]

It works from a non google environment. We have a service running on AWS
which is working smooth. It's not a whitelist problem because these are
signed calls which do not account for rate limiting based on IP.

Someone from google has replied saying the problem is not on their end. I
have raised an issue on the twitter discussion forum (stupid of me to not
have done that simultaneously).



On 26 October 2011 18:33, Brandon Wirtz  wrote:

> So you think that Fetches to only Twitter and FB are broken?   Did you try
> from a non-Goog Environment?  There are Fail Whales all over today.   
>
> ** **
>
> And if you are running “Hundreds of API calls a minute” you are likely
> hitting the API IP Limits since Twitter won’t grant a white list for Google
> IP’s.
>
> ** **
>
> You should be using a proxy to access twitter through a single IP what is
> on the Twitter API white List.
>
> ** **
>
> ** **
>
> *From:* google-appengine@googlegroups.com [mailto:
> google-appengine@googlegroups.com] *On Behalf Of *nischalshetty
> *Sent:* Wednesday, October 26, 2011 12:11 PM
> *To:* google-appengine@googlegroups.com
> *Subject:* Re: [google-appengine] URLFetch is timing out excessively
>
> ** **
>
> I agree twitter times out but this is not because of them. I'm talking
> about hundreds of timeout every minute.
>
> ** **
>
> We have things in place to retry timeouts, but I'm talkin about timeouts
> even after 3 retries with a timeout of 20 second each. 
>
> ** **
>
> ** **
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/YJ2bm0bM_l8J.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
-Nischal
twitter: NischalShetty 
facebook: Nischal 

 

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

RE: [google-appengine] Re: Emails sent from GAE apps to yahoo or hotmail addresses get tagged as spam

[Brandon Wirtz]

Fill out the paperwork, and attend the seminar on LiveMail White Listing.
Takes about 12 hours and then your domain is white listed on Hotmail, Live
Mail, and Yahoo Mail.  The cost is something like $200 and well worth it.
They do the seminars 4 times a year.

-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Kaan Soral
Sent: Wednesday, October 26, 2011 12:09 PM
To: Google App Engine
Subject: [google-appengine] Re: Emails sent from GAE apps to yahoo or
hotmail addresses get tagged as spam

Nope, you shouldn't make users think, a lot of them will just get confused

On Oct 26, 2:45 pm, Joshua Smith  wrote:
> Perhaps we're all pushing the rock uphill when we really should be letting
it roll downhill:
>
> Anyone ever try doing a user registration like this:
>
> - Generate a mailto URL with the app as the addressee, and the subject set
to a token:
>
> mailto:regis...@myapp.appspotmail.com?subject=a9b8c7d6e5f
>
> - The user clicks that link, and sends the message
>
> - Using polling or a channel the page waits for appengine to get their 
> email
>
> - When the server gets the mail, you create the registered account
>
> - Remind the user what email address they should use to log in, since 
> you know it from their email, and they might not be too clear on what 
> their email address really is (a frighteningly common occurrence, I've 
> noticed)
>
> Thoughts?
>
> On Oct 26, 2011, at 1:25 AM, Tapir wrote:
>
>
>
>
>
>
>
> > Yes, my app has been experiencing this problem for a long time.
> > Half of my app new users will not activate their accounts.
> > I found some of them try to register a new account with the last 
> > just created account inactivated.
> > So I guess they haven't received the activation mails.
>
> > I haven't got a efficient way to fix this problem.
> > The problem is I don't know whether of not the new users have 
> > received the activation mails.
> > There is no way to determine whether the activation mails are sent 
> > successfully or not.
>
> > I have put a obvious notification at the top of each page for 
> > inactivated users.
> > But the rate of activated accounts is still not increased.
>
> > On Oct 25, 8:48 am, Rishi Arora  wrote:
> >> I have only see this thread on the
subject:http://groups.google.com/group/google-appengine/browse_thread/thread
/...
> >> And the resolution was to move to Amazon SES or other 3rd party 
> >> email service providers.
>
> >> Anyone experienced this lately, and have any suggestions on how to 
> >> avoid being marked as spam?  The emails I generate are mostly "email
confirmation"
> >> type emails, where I generate a 64-byte random string to be used in 
> >> URL that the recipient clicks on to confirm that they are the owner 
> >> of the said email account.  The email, in my case, originates from 
> >> u...@appi-id.appspotmail.com, and I'm setting the reply-to field to 
> >> my google apps domain, which is obviously different from the GAE app
domain.
> >>  Perhaps I should not override the "reply-to" field in the header 
> >> of the emails I send.  This might be somewhat of an inconvenience in
some cases.
>
> >> Thanks in advance.
>
> > --
> > You received this message because you are subscribed to the Google
Groups "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group
athttp://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-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.


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

RE: [google-appengine] URLFetch is timing out excessively

[Brandon Wirtz]

So you think that Fetches to only Twitter and FB are broken?   Did you try
from a non-Goog Environment?  There are Fail Whales all over today.   

 

And if you are running "Hundreds of API calls a minute" you are likely
hitting the API IP Limits since Twitter won't grant a white list for Google
IP's.

 

You should be using a proxy to access twitter through a single IP what is on
the Twitter API white List.

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of nischalshetty
Sent: Wednesday, October 26, 2011 12:11 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] URLFetch is timing out excessively

 

I agree twitter times out but this is not because of them. I'm talking about
hundreds of timeout every minute.

 

We have things in place to retry timeouts, but I'm talkin about timeouts
even after 3 retries with a timeout of 20 second each. 

 

 

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

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

[google-appengine] blobstore file

[Mark Jen]

Hi,

I've run into a problem using the file API for blobstore 
(http://code.google.com/appengine/docs/python/blobstore/overview.html#Writing_Files_to_the_Blobstore)
 on 
dev_appserver.py with --high_replication. It seems that after 
files.finalize(file_name) is called, the blob_key is not immediately 
available. Is this a known issue? I couldn't find it here 
(http://code.google.com/p/googleappengine/issues/list).

Thanks,
Mark

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

[google-appengine] Re: URLFetch is timing out excessively

[Vivek Puri]

Thank you.

On Oct 26, 3:30 pm, Nischal Shetty  wrote:
> Done. I too have raised a production issue 
> -http://code.google.com/p/googleappengine/issues/detail?id=6188
>
> On 26 October 2011 16:25, Vivek Puri  wrote:
>
>
>
>
>
>
>
>
>
> > Nischal, please star -
> >http://code.google.com/p/googleappengine/issues/detail?id=6189
>
> > On Oct 26, 3:20 pm, Vivek Puri  wrote:
> > > +1 . Requests to Facebook are also timing out.
>
> > > On Oct 26, 3:10 pm, nischalshetty  wrote:
>
> > > > I agree twitter times out but this is not because of them. I'm talking
> > > > about hundreds of timeout every minute.
>
> > > > We have things in place to retry timeouts, but I'm talkin about
> > timeouts
> > > > even after 3 retries with a timeout of 20 second each.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> -Nischal
> twitter: NischalShetty 
> facebook: Nischal 
>
>      

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

Re: [google-appengine] Re: URLFetch is timing out excessively

[Nischal Shetty]

Done. I too have raised a production issue -
http://code.google.com/p/googleappengine/issues/detail?id=6188

On 26 October 2011 16:25, Vivek Puri  wrote:

> Nischal, please star -
> http://code.google.com/p/googleappengine/issues/detail?id=6189
>
> On Oct 26, 3:20 pm, Vivek Puri  wrote:
> > +1 . Requests to Facebook are also timing out.
> >
> > On Oct 26, 3:10 pm, nischalshetty  wrote:
> >
> >
> >
> >
> >
> >
> >
> > > I agree twitter times out but this is not because of them. I'm talking
> > > about hundreds of timeout every minute.
> >
> > > We have things in place to retry timeouts, but I'm talkin about
> timeouts
> > > even after 3 retries with a timeout of 20 second each.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
-Nischal
twitter: NischalShetty 
facebook: Nischal 

 

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

[google-appengine] Re: URLFetch is timing out excessively

[Vivek Puri]

Nischal, please star - 
http://code.google.com/p/googleappengine/issues/detail?id=6189

On Oct 26, 3:20 pm, Vivek Puri  wrote:
> +1 . Requests to Facebook are also timing out.
>
> On Oct 26, 3:10 pm, nischalshetty  wrote:
>
>
>
>
>
>
>
> > I agree twitter times out but this is not because of them. I'm talking
> > about hundreds of timeout every minute.
>
> > We have things in place to retry timeouts, but I'm talkin about timeouts
> > even after 3 retries with a timeout of 20 second each.

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

[google-appengine] Re: URLFetch is timing out excessively

[Vivek Puri]

+1 . Requests to Facebook are also timing out.


On Oct 26, 3:10 pm, nischalshetty  wrote:
> I agree twitter times out but this is not because of them. I'm talking
> about hundreds of timeout every minute.
>
> We have things in place to retry timeouts, but I'm talkin about timeouts
> even after 3 retries with a timeout of 20 second each.

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

Re: [google-appengine] URLFetch is timing out excessively

[nischalshetty]

I agree twitter times out but this is not because of them. I'm talking 
about hundreds of timeout every minute.

We have things in place to retry timeouts, but I'm talkin about timeouts 
even after 3 retries with a timeout of 20 second each. 


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

[google-appengine] Re: Emails sent from GAE apps to yahoo or hotmail addresses get tagged as spam

[Kaan Soral]

Nope, you shouldn't make users think, a lot of them will just get
confused

On Oct 26, 2:45 pm, Joshua Smith  wrote:
> Perhaps we're all pushing the rock uphill when we really should be letting it 
> roll downhill:
>
> Anyone ever try doing a user registration like this:
>
> - Generate a mailto URL with the app as the addressee, and the subject set to 
> a token:
>
> mailto:regis...@myapp.appspotmail.com?subject=a9b8c7d6e5f
>
> - The user clicks that link, and sends the message
>
> - Using polling or a channel the page waits for appengine to get their email
>
> - When the server gets the mail, you create the registered account
>
> - Remind the user what email address they should use to log in, since you 
> know it from their email, and they might not be too clear on what their email 
> address really is (a frighteningly common occurrence, I've noticed)
>
> Thoughts?
>
> On Oct 26, 2011, at 1:25 AM, Tapir wrote:
>
>
>
>
>
>
>
> > Yes, my app has been experiencing this problem for a long time.
> > Half of my app new users will not activate their accounts.
> > I found some of them try to register a new account with the last just
> > created account inactivated.
> > So I guess they haven't received the activation mails.
>
> > I haven't got a efficient way to fix this problem.
> > The problem is I don't know whether of not the new users have received
> > the activation mails.
> > There is no way to determine whether the activation mails are sent
> > successfully or not.
>
> > I have put a obvious notification at the top of each page for
> > inactivated users.
> > But the rate of activated accounts is still not increased.
>
> > On Oct 25, 8:48 am, Rishi Arora  wrote:
> >> I have only see this thread on the 
> >> subject:http://groups.google.com/group/google-appengine/browse_thread/thread/...
> >> And the resolution was to move to Amazon SES or other 3rd party email
> >> service providers.
>
> >> Anyone experienced this lately, and have any suggestions on how to avoid
> >> being marked as spam?  The emails I generate are mostly "email 
> >> confirmation"
> >> type emails, where I generate a 64-byte random string to be used in URL 
> >> that
> >> the recipient clicks on to confirm that they are the owner of the said 
> >> email
> >> account.  The email, in my case, originates from
> >> u...@appi-id.appspotmail.com, and I'm setting the reply-to field to my
> >> google apps domain, which is obviously different from the GAE app domain.
> >>  Perhaps I should not override the "reply-to" field in the header of the
> >> emails I send.  This might be somewhat of an inconvenience in some cases.
>
> >> Thanks in advance.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to 
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group 
> > athttp://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-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Ask for help :GAE can't work

[Will]

Do you intend to use GAE to overcome GFW? That won't work because GAE
itself is blocked by GFW.

Or are you looking for a way to bypass GFW so that you can access your
GAE app within China? If so, you can consider reverse proxy. It works
for me.

Will

On Sat, Oct 22, 2011 at 12:06 AM, pengcehng oy  wrote:
> Hi，I'm a Chinese college student .I was seeking to cross the GFW with
> the help of GAE , GAppProxy and wallproxy.However, when I try to use
> it as this guider(http://www.labnol.org/internet/setup-proxy-server/
> 12890/) ,　I found my Google App Engine didn't work(http://
> ouxiaohan.appspot.com/fetch.py) ,and I couldn't find out the reason.Is
> there anybody who can teach me find a solution? Thanks a lot.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

RE: [google-appengine] URLFetch is timing out excessively

[Brandon Wirtz]

Raise the issue with twitter.  They time out because twitter is too slow.
Not Google.  This is a common problem with twitter. 

 

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of nischalshetty
Sent: Wednesday, October 26, 2011 10:54 AM
To: google-appengine@googlegroups.com
Subject: [google-appengine] URLFetch is timing out excessively

 

I've raised a production issue around 4 hours ago but no one has been able
to look into it yet :(

 

Requests to twitter are timing out excessively. Since we have twitter login,
users are not even able to login to the application. Can someone please look
into this? 

 

http://code.google.com/p/googleappengine/issues/detail?id=6188

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

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

[google-appengine] URLFetch is timing out excessively

[nischalshetty]

I've raised a production issue around 4 hours ago but no one has been able 
to look into it yet :(

Requests to twitter are timing out excessively. Since we have twitter 
login, users are not even able to login to the application. Can someone 
please look into this? 

http://code.google.com/p/googleappengine/issues/detail?id=6188

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

[google-appengine] versioning tool for Google App Engine code samples

[Lucas]

Hello!
I´m new to Google App Engine and I have the following question:
What kind of versioning software/tools should I use in order to clone
the code for sample applications that run on Google App Engine from
this link http://code.google.com/p/google-app-engine-samples/ ?
May I integrate that software into Eclipse?

Many thanks in advance!

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

[google-appengine] Server Errors - Timeouts. Free accounts getting inferior service?

[David Manns]

This morning (and many times over recent weeks) my application, which 
normally runs perfectly, encounters both very slow response times as well as 
these server errors.  When I look at the logs, the errors are timeouts.  The 
application uses the web2py framework.  The problem occurs both on the 
initial screen either a login screen or a search form, depending on whether 
a persistent login has been used - in either case no datastore access, and 
at random times during a sequence of searches and edits of the database.

Perhaps related to business hours, often works more consistently off peak 
hours.  Are free applications now being discriminated against and being 
relegated to a small group of, at times, overloaded servers?

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

[google-appengine] Application Architecture

[Rick Mangi]

Hello all,

I'm working on an application which will consist of a set of java
services on top of bigtable/blobstore, a user facing website, a CMS
and feeds for mobile devices.

I'm trying to decide what the best way to separate the application out
to allow for easier deployments and also to allow the application to
scale better. It seems to me that since the usage patterns for the
various components will be so different that appengine would probably
do a better job of scaling up/down if we broke out the components into
at least 3, if not 4 separate applications

1. Service tier (access to data and blobs)
2. website
3. CMS
4. Mobile feeds

Possibly it would make sense to combine 1 & 4. In this scenario, the
website and CMS would access the service tier using urlfetch to get
json/xml feeds.

My questions are these:

1. Does that make sense? Am I correct in assuming that combining all
of these pieces into 1 big deployment will make autoscaling much
slower (startup time) and less predictable?

2. What is the performance of fetching urls from other appengine
servers? Is it optimized in terms of network latency or do the
requests go out to the internet and back to google?

3. Are we better off deploying these as separate "versions" of the
same application and sharing our common data access code as a jar
file?

Note: I'm aware of the TOS around multiple applications, I'm not
concerned about it. We're not trying to bypass anything, just trying
to make this scale :-)


Thanks in advance for any feedback or suggestions.

Rick

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

[google-appengine] deployement to google failed

[Abderrahim AGDICHE]

Hello!
When i try de debloy ma webDb to google i receive this:
--
2011-10-24 11:32:20 Running command: "['C:\\Python25\\pythonw.exe', '-
u', 'C:\\Program Files\\Google\\google_appengine\\appcfg.py', '--
no_cookies', u'--email=a.agdi...@gmail.com', '--passin', 'update', 'D:\
\customtinywebdb\\customtinywebdb']"
Error parsing yaml file:
mapping values are not allowed here
  in "D:\customtinywebdb\customtinywebdb\app.yaml", line 1, column 22
2011-10-24 11:32:22 (Process exited with code 1)

You can close this window now.
--

Can some body help me to resolve this, also there is no sample datas
in "customtinywebdb" ??

Thank you.

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

[google-appengine] Ask for help :GAE can't work

[pengcehng oy]

Hi，I'm a Chinese college student .I was seeking to cross the GFW with
the help of GAE , GAppProxy and wallproxy.However, when I try to use
it as this guider(http://www.labnol.org/internet/setup-proxy-server/
12890/) ,　I found my Google App Engine didn't work(http://
ouxiaohan.appspot.com/fetch.py) ,and I couldn't find out the reason.Is
there anybody who can teach me find a solution? Thanks a lot.

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

[google-appengine] Help! : Unable to create a new session key. taking down my whole site!

[alvin.fezzl]

I'm very frustrated over this; more than enough angry users are
breathing down my neck at the moment.

Django crashing for no reason, and all I get is this error:

: Unable to create a new session key.
Traceback (most recent call last):
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/appenginepatch/main.py", line 36, in real_main
util.run_wsgi_app(application)
  File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/util.py", line 98, in run_wsgi_app
run_bare_wsgi_app(add_wsgi_middleware(application))
  File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/util.py", line 116, in run_bare_wsgi_app
result = application(env, _start_response)
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/core/handlers/wsgi.py", line
241, in __call__
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/core/handlers/base.py", line
73, in get_response
  File "/base/python_runtime/python_dist/lib/python2.5/locale.py",
line 16, in process_request
# Try importing the _locale module.
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
libs/__init__.py", line 97, in get_language_from_request

  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/utils/translation/
trans_real.py", line 358, in get_language_from_request
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/contrib/sessions/backends/
base.py", line 63, in get
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/contrib/sessions/backends/
base.py", line 172, in _get_session
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/contrib/sessions/backends/
cache.py", line 16, in load
  File "/base/data/home/apps/s~zuupycrowddeals/1.354207428598899588/
common/zip-packages/django-1.1.zip/django/contrib/sessions/backends/
cache.py", line 33, in create

Any solutions?

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

[google-appengine] Problem with app.yaml include "reportlab" : No module name

[Emad Maleki]

Hi Everybody
I have sever problem with GAE, I am pretty new in this stuff but i
frastrated googling about 3 days to find proper answer.
here is the challenge
I have installed reportlab to produce PDF files. but i dont know how
to fix the path, library and app.yaml things in order no to have : No module named reportlab.lib.pagesizes
error:

Please someone simply describe what should some one do , when he wants
to use external library in GOOGLE APP ENgine

here is my app.yaml file

application: pdft
version: 1
runtime: python
api_version: 1

handlers:
- url: /favicon.ico
  static_files: static/shared/favicon.ico
  upload: static/shared/favicon.ico

- url: /reportlab
  static_dir: reportlab

- url: /.*
  script: test.py

here is my code

from reportlab.lib.pagesizes import A4
from reportlab.pdfgen import canvas

.


Thank you in advanced,
Emad


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

[google-appengine] Re: The Dining Philosophers

[Kyle]

Is there a reason that you didn't use the memcached service to
implement semaphores?

-Kyle

On Oct 23, 6:23 am, Emlyn  wrote:
> Here's a new AppEngine article from me, "The Dining Philosophers". It
> includes a full working implementation of Semaphores using the
> Datastore, and implementation of flawed and successful solutions to
> the classic Dining Philosophers problem using Semaphores.
>
> http://appenginedevelopment.blogspot.com/2011/10/dining-philosophers
>
> Fun for hard core comp sci types ;-)
>
> --
> Emlyn
>
> http://my.syyn.cc- Synchonise Google+, Facebook, WordPress and Google
> Buzz posts,
> comments and all.http://point7.wordpress.com- My blog
> Find me on Facebook and Buzz

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

[google-appengine] Permanent failure attempting to execute task

[jason]

Hi,

Just saw this a few days ago while using the mail API:

Permanent failure attempting to execute task
Traceback (most recent call last):
  File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/deferred/deferred.py", line 271, in post
run(self.request.body)
  File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/deferred/deferred.py", line 129, in run
raise PermanentTaskFailure(e)
PermanentTaskFailure: No module named backends.base

Does anybody know why this might happen on a recent deploy?

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

[google-appengine] Site permanently broken/offline?

[pman74]

Hi there,

I've been trying for months to access
http://app-store.appspot.com

Only message I get is

Sorry, an error has occurred.

We're working on getting this fixed as soon as we can.

A truly verbose means of telling you something went wrong.
If only the "As soon as we can" did not mean "Problem has not been
tackled for several months".
What exactly is up there?
It could - of course - only be a programmer's error which triggers
this error page.
Nor is there any way to tell the developer about it because everything
is hermetically closed like a fortress.

That's why I'm trying to post about the issue here now. (Even though I
think it's rather pointless)

-pm

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

Re: [google-appengine] SaaS for government on GAE

[Joshua Smith]

www.mytowngovernment.org

On Oct 26, 2011, at 12:09 PM, Jacob Gur wrote:

> Are there any examples out there of 3rd party services running on GAE whom 
> have government clients, and/or government agencies themselves who have 
> deployed on GAE?
> 
> 
> On Mon, Oct 24, 2011 at 6:13 PM, hector@ISB  wrote:
> I don't think that there would be policy specific to GAE, or AWS for that 
> matter.  What I've seen (NIH) is mostly concerned with standards for securing 
> private data (e.g. passwords, SSL, etc), portability and auditing.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To view this discussion on the web visit 
> https://groups.google.com/d/msg/google-appengine/-/17BZl4605CoJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.

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

[google-appengine] Re: Remove logging from app engine

[Brian Williams]

Thank you for all your advice. 

Now using Shivalwolfs webemail2 using post. Had made mistake in original 
codeblock in AI which ommitted the 's' on the http//myapp.appspot.com url. 
This was causing bounce code 302. Now it works very well. Thank you Shival!

What worked for the logging was simply removing the logging reference to 
the data in the .py file. I made a number of errors in my first attempt 
which corrupted the code but after a long walk I started from scratch and 
it worked. Can now see requests and confirmations but no actual data. 

This noob now feels like he is getting somewhere. 

Thank you all.

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

[google-appengine] Re: Announcing SSL for Custom Domains Trusted Tester Program

[Jesse]

Hi Cayden,

Thanks for the hard work on this.  I'd like to suggest 2 features (they may 
already be in the works):

 * UCC on VIP
 * Wildcard on VIP

If VIP potentially costs $100/mon (not final I know) it would be really 
nice if I could issue a UCC cert for my VIP address and setup routing to n 
number of apps (this is particularly important for testing staging 
environments, I do not want to pay for a different SNI or VIP for *each* 
testing/staging app that I have deployed, if possible).  In our testing UCC 
is very well supported. 

Wildcard would be similar but obviously the sub-domain hosts would not be 
known beforehand by the cert.  The routing would need some sort of 
interface to configure it.  We have a lot of services under master domains 
and so this would be helpful. 

Best,

jesse


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

Re: [google-appengine] Re: SaaS for government on GAE

[Jacob Gur]

Are there any examples out there of 3rd party services running on GAE whom
have government clients, and/or government agencies themselves who have
deployed on GAE?


On Mon, Oct 24, 2011 at 6:13 PM, hector@ISB  wrote:

> I don't think that there would be policy specific to GAE, or AWS for that
> matter.  What I've seen (NIH) is mostly concerned with standards for
> securing private data (e.g. passwords, SSL, etc), portability and auditing.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/17BZl4605CoJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

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

Re: [google-appengine] GAE problem in Eclipse

[Sébastien Tromp]

On Fri, Oct 7, 2011 at 1:46 PM, Pierre-Henry Perret  wrote:
>
> Hello,
> A maven  project , which compiles and runs, appears with resource path
> problem in the Eclipse IDE:
> ___
> Description Resource Path Type Location
> The App Engine SDK
> 'C:\Users\Pierre\.m2\repository\com\google\appengine\appengine-api-1.0-sdk\1.5.4\appengine-api-1.0-sdk-1.5.4.jar'
> on the project's build path is not valid (SDK location
> 'C:\Users\Pierre\.m2\repository\com\google\appengine\appengine-api-1.0-sdk\1.5.4\appengine-api-1.0-sdk-1.5.4.jar'
> is not a directory) gwtp-sample-basic Google App Engine Problem Unknown
> 
>
> It looks like the Elcipse plugin append '.jar' to the GAE path.
> Has  someone ever seen a message like that ?

You should check your project build path / order and export tab. The
Maven dependencies should be listed *after* the GAE jars. Once you do
so, double-check the SDK used by your project (project / properties /
google).
-- 
Sébastien Tromp

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

Re: [google-appengine] Emails sent from GAE apps to yahoo or hotmail addresses get tagged as spam

[Joshua Smith]

Perhaps we're all pushing the rock uphill when we really should be letting it 
roll downhill:

Anyone ever try doing a user registration like this:

- Generate a mailto URL with the app as the addressee, and the subject set to a 
token:

mailto:regis...@myapp.appspotmail.com?subject=a9b8c7d6e5f

- The user clicks that link, and sends the message

- Using polling or a channel the page waits for appengine to get their email

- When the server gets the mail, you create the registered account

- Remind the user what email address they should use to log in, since you know 
it from their email, and they might not be too clear on what their email 
address really is (a frighteningly common occurrence, I've noticed)

Thoughts?

On Oct 26, 2011, at 1:25 AM, Tapir wrote:

> Yes, my app has been experiencing this problem for a long time.
> Half of my app new users will not activate their accounts.
> I found some of them try to register a new account with the last just
> created account inactivated.
> So I guess they haven't received the activation mails.
> 
> I haven't got a efficient way to fix this problem.
> The problem is I don't know whether of not the new users have received
> the activation mails.
> There is no way to determine whether the activation mails are sent
> successfully or not.
> 
> I have put a obvious notification at the top of each page for
> inactivated users.
> But the rate of activated accounts is still not increased.
> 
> On Oct 25, 8:48 am, Rishi Arora  wrote:
>> I have only see this thread on the 
>> subject:http://groups.google.com/group/google-appengine/browse_thread/thread/...
>> And the resolution was to move to Amazon SES or other 3rd party email
>> service providers.
>> 
>> Anyone experienced this lately, and have any suggestions on how to avoid
>> being marked as spam?  The emails I generate are mostly "email confirmation"
>> type emails, where I generate a 64-byte random string to be used in URL that
>> the recipient clicks on to confirm that they are the owner of the said email
>> account.  The email, in my case, originates from
>> u...@appi-id.appspotmail.com, and I'm setting the reply-to field to my
>> google apps domain, which is obviously different from the GAE app domain.
>>  Perhaps I should not override the "reply-to" field in the header of the
>> emails I send.  This might be somewhat of an inconvenience in some cases.
>> 
>> Thanks in advance.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> 

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

[google-appengine] Re: GWT 2.4.0/GAE: java.lang.ClassNotFoundException: javax.validation.Path

[ZS]

I solved this by adding gwt-servlet-deps.jar to war/WEB-INF/lib and then to 
the classpath!

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

[google-appengine] Re: KindError Question

[Zeeple]

Two things more:

1. Turns out the edit script isn't working either, so at least the
behavior is more consistent (in my mind)
2. I think it might have something to do with the idea that when you
pass any info over a URL var, it shows up at the other end as a string
(no longer a key). Not real sure tho... still experimenting...

TFL, Z.

On Oct 25, 9:40 pm, Zeeple  wrote:
> Hi folks, this error does not make sense to me:
>
> KindError: Kind 'MemberRecord' is not a subclass of kind
> 'MemberRecord'
>
> Here is how it was generated:  My fledgling app is a simple membership
> management database which I display in a table.  Each row of the table
> includes an item 'edit' and an item 'delete'.  These two items are
> links formed like this:
>
>         {% ifequal user.atleast2 'True' %}
>           edit td>
>         {% endifequal %}
>         {% ifequal user.atleast3 'True' %}
>           delete td>
>         {% endifequal %}
>
> That part works just fine.  So in the edit.py an del.py get() handlers
> I have logic to manipulate the database as required. The edit script
> works perfectly.  The del.py script produces the above error.  Here is
> how I am trying to delete the record:
>
> class Handler(webapp.RequestHandler):
>     def get(self):
>                 entity_to_del = self.request.get('del')
>                 rec = d.MemberRecord.get(entity_to_del)
>                 rec.delete()
>
>                 self.redirect('/membership/view')
>
> This method of using a url variable for passing a key to the scripts
> seems to be solid. It works as expected for editing datastore entities
> but not for deleting them.  Any ideas as to what I could be running
> into?

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