Re: [google-appengine] how can I do a GAE project without .appspot.com

[Deepak Singh]

Thats not possible because all appengine applications are served through
app-id.appspot.com

Regards
Deepak

On Tue, Aug 7, 2012 at 11:15 AM, Shilendra Sharma wrote:

>
> Hi.. All
>
> how can I do a gae project without .appspot.com. bcoz till now I am using
> this with appspot.com but when I search this by any search engine like
> google it not found it need the full url for this application
>
> --
> 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/-/_7Mf1aYzdvsJ.
> 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.
>



-- 
Deepak Singh

-- 
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] Backend performance, compared

[rerng...@gmail.com]

Very interesting result.

Sent from my HTC

- Reply message -
From: "Jeff Schnitzer" 
To: "Google App Engine" 
Subject: [google-appengine] Backend performance, compared
Date: Wed, Aug 8, 2012 09:10


If you've been reading various threads on this list you know that
Richard has been having trouble getting his mobile game to run
smoothly on GAE.  It's a little unusual because timing is coordinated
precisely:

 * At T+0, all clients submit scores
 * At T+5s, a reaper process aggregates the scores and builds a result set
 * At T+10s, all clients fetch scores

The question is:  Where to submit the score data so that the reaper
can fetch and aggregate it?

Here's some answers that didn't work:

 * The datastore.  Eventual consistency is too eventual to query for
all the scores and get them.
 * Pull queues.  There's too much of a delay between task insertion
and when it appears for leasing.
 * A single backend.  One backend cannot handle more than ~80qps.

He eventually got a system working reliably, sharded across ten B1
instances, at a cost (beyond other charges) of ~$600/mo.  It can
collect a couple thousand scores within the 5s deadline (barely).

I thought this was insane, so I built a few experiments to see what
other technologies can do, using the exact program logic of Richard's
collector.  Here are the results:

The environment:  256MB Rackspacecloud VPS running Ubuntu 10.04.4 LTS
The cost:  $11/mo
The command:  ab -c 1 -n 1 -r http://theurl  (that's 10k
requests, all concurrent).

Node.js:  ~2500 qps.  Rock solid through multiple test runs, all
complete before the deadline.
Java SimpleHTTP:  ~2100 qps.  Had to bump heap up to 128MB.
Python Twisted:  ~1600 qps.  Failed a lot of requests on most test runs.
Python Tornado:  ~1500 qps, but rock solid through multiple test runs.

So basically, an $11/mo VPS server running Javascript vastly exceeds
the capabilities of 10 backends at $60/mo each.

Jeff

-- 
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] Unique Integer ID for a non primary key field for Entities in Google App Engine

[Neo]

Hi Jeff and Michael,

Yes, I am looking for a way to ensure that multiple servers don't create 
the same URLInfo object at the same time.

As Michael said: If you use a transaction to retrieve the entity by key 
(the URL) and then create one if it doesn't exist, only one entity should 
be successfully created in the event of a collision. Therefore, *even if 
you create two different versions with different unique ids,* only one 
should survive.

My question is do we really need to care about the lost Id (as only one 
entity is going to survive) in the case of collision? And can we have code 
snippet for allocating and assigning id to the URLInfo in the transaction 
that guarantees that there shall be only one instance of a URL in the 
datastore and the Ids of all the URLs are unique and non empty?

Thanks for your patience.

-- 
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/-/9LXWEKXdndQJ.
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] Backend performance, compared

[Jeff Schnitzer]

If you've been reading various threads on this list you know that
Richard has been having trouble getting his mobile game to run
smoothly on GAE.  It's a little unusual because timing is coordinated
precisely:

 * At T+0, all clients submit scores
 * At T+5s, a reaper process aggregates the scores and builds a result set
 * At T+10s, all clients fetch scores

The question is:  Where to submit the score data so that the reaper
can fetch and aggregate it?

Here's some answers that didn't work:

 * The datastore.  Eventual consistency is too eventual to query for
all the scores and get them.
 * Pull queues.  There's too much of a delay between task insertion
and when it appears for leasing.
 * A single backend.  One backend cannot handle more than ~80qps.

He eventually got a system working reliably, sharded across ten B1
instances, at a cost (beyond other charges) of ~$600/mo.  It can
collect a couple thousand scores within the 5s deadline (barely).

I thought this was insane, so I built a few experiments to see what
other technologies can do, using the exact program logic of Richard's
collector.  Here are the results:

The environment:  256MB Rackspacecloud VPS running Ubuntu 10.04.4 LTS
The cost:  $11/mo
The command:  ab -c 1 -n 1 -r http://theurl  (that's 10k
requests, all concurrent).

Node.js:  ~2500 qps.  Rock solid through multiple test runs, all
complete before the deadline.
Java SimpleHTTP:  ~2100 qps.  Had to bump heap up to 128MB.
Python Twisted:  ~1600 qps.  Failed a lot of requests on most test runs.
Python Tornado:  ~1500 qps, but rock solid through multiple test runs.

So basically, an $11/mo VPS server running Javascript vastly exceeds
the capabilities of 10 backends at $60/mo each.

Jeff

-- 
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] Computationally complex done fast: Was What are the Pros

[Jeff Schnitzer]

On Mon, Aug 6, 2012 at 2:41 PM, Drake  wrote:
> So here are more generalizations for APP Engine:
>
> Cache Everything:
> Your CPU is slow, when profiling weigh the CPU to the memory cost and speed
> for things which you calculate often. It is surprising that even simple
> stuff denormalized can be so much faster than the complex operation.
> GetByID("Sales-and-Shipping-AZ-1599-1lb") takes less than 3 MS out of
> Instance memory cache served from a dedicated backend, 10ms from memcache
> 120ms from data store.  You can't do the 4 lookups and the calculation that
> fast. So Don't.  Remember all your "Complex business rules" are cacheable.
> Anything worth doing is worth caching :-)

These numbers are nothing like my past experimental results, so I ran
them again.  Here's appstats for a calls from a F1 to a B1 that does
nothing but return the string "noop":

https://img.skitch.com/20120808-nn749683wqdg5516fy732k71iw.jpg

Clicking on those links shows that 99% of the time is spent waiting on
urlfetch to the backend.

 * The _minimum_ fetch time to a backend is 12ms.

 * Maybe 10% of calls are >250ms, and a very significant portion exceed 500ms.

 * I also tried this with a B8.  No material difference
(https://img.skitch.com/20120808-gerejtgfd958i691hsiw897wjw.jpg)

My experience with memcache is that most requests come back in 2ms or
less, but there are rare outliers in the 100ms or 200ms range.  Much,
much better behaved.

BTW this was with zero contention (ab -c 1 -n 50).

Conclusion:  Backends suck.

Jeff

-- 
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: Wildcard in web.xml creates infinite directories?

[hyperflame]

If crawlers are requesting deals/deals/deal-name instead of deals/deal-
name, that means that someone is linking to your site ( or you're
linking to your own site ) with the first method. You might want to
double check that your internal links, and any links that you're
promoting, are correctly written. It's easy to accidentally do this,
especially when you're using relative links.

If you can't find anything wrong, then you can write some code into
your Deal servlet to correctly route the request. Use getRequestURI
( 
http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI()
) to get the path the request used. If you find "deals" twice in the
path, you can issue a 301 Moved Permanently, then redirect the client
to deals/deal-name appropriately. Crawlers won't penalize you for a
301.

On Aug 7, 8:04 pm, Phil McDonnell  wrote:
> Apparently, I am creating infinite sub-directories from a web crawler's
> perspective due to a wildcard I have in my web.xml.  I have a single jsp
> file that dynamically handles all requests to the directory
> mysite.com/deals/*. The goal here was for the jsp to handle
> mysite.com/deals/some-deal-name-here.  However, crawlers apparently are
> also picking up on mysite.com/deals/deals/some-deal-name-herewhich
> unfortunately looks like duplicate content from a web crawler
> perspective.  This is not good for search ranking. Is there a way to
> configure my web.xml in order to stop this from happening?
>
> *Here's what I have in my web.xml:*
> 
>         deal
>         */deals/**
> 
> 
>     deal
>     /deal.jsp
> 
>
> *Here's what I tried to fix it:*
> 
>         deal
>         */deals/[a-z0-9_A-Z-]**
> 
> 
>      deal
>      /deal.jsp
> 
>
> Any ideas for other ways to potentially configure this?
>
> Thanks,
> Phil

-- 
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] Task Queue "default"

[Amy Unruh]

hi,

You can always access/use the queue of that name even if you don't have any
queue.yaml definitions.  So it's default in that sense.  You can redefine
the default queue specs in the queue.yaml file if you want, but you can use
it even if you do not do so.

On 8 August 2012 03:31, Fábio Peruchi  wrote:

> Hi!
>
> Does anyone know what's the purpose of the "*default*" Task Queue?
>
> Fábio
>
> --
> 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] Wildcard in web.xml creates infinite directories?

[Phil McDonnell]

Apparently, I am creating infinite sub-directories from a web crawler's
perspective due to a wildcard I have in my web.xml.  I have a single jsp
file that dynamically handles all requests to the directory
mysite.com/deals/*. The goal here was for the jsp to handle
mysite.com/deals/some-deal-name-here.  However, crawlers apparently are
also picking up on mysite.com/deals/deals/some-deal-name-herewhich
unfortunately looks like duplicate content from a web crawler
perspective.  This is not good for search ranking. Is there a way to
configure my web.xml in order to stop this from happening?

*Here's what I have in my web.xml:*

deal
*/deals/**


deal
/deal.jsp


*Here's what I tried to fix it:*

deal
*/deals/[a-z0-9_A-Z-]**


 deal
 /deal.jsp


Any ideas for other ways to potentially configure this?

Thanks,
Phil

-- 
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] APP DOWN due to some sort of undocumented Google security system

[Chris Ramsdale]

Would you mind sending me (via direct email) your app ID(s) and we'll look
into this?  We're aware of Checkout/Wallet issues and are improving the
user experience...I promise.

-- Chris


On Tue, Aug 7, 2012 at 12:51 AM, Jon Stevens  wrote:

> Chris,
>
> I've tried to setup billing on my appid three times now. I set it up
> and then it seems to turn off on its own without even sending me an
> email or any notification.
>
> Every few days, I check and it keeps saying that I have a new past due
> bill. When I go to turn it on again, it asks me for a new shipping
> address (even though I already have two duplicate addresses in the
> select box... one was from the last time I tried to set it up and I'm
> not even shipping anything!?!).
>
> Now that I'm on the checkout page trying to *pay you money*, I can
> also see that there is a javascript error on the page, which is
> preventing any clicks on buttons from working.
>
> This is seriously the work of amateurs, I really expect more quality
> and testing from you guys before you put stuff like this into
> production. Please, let me know when you have billing for my appid
> fixed. If you can't figure it out, feel free to contact me privately.
>
> jon
>
>
> On Mon, Aug 6, 2012 at 4:12 PM, Chris Ramsdale 
> wrote:
> > Rick,
> >
> > We publish upcoming features and functionality within the "App Engine
> > Features" section of our developer site:
> >
> > https://developers.google.com/appengine/docs/features
> >
> > In regards to bailing on the platform, it is unfortunate to hear.  If you
> > have time, I would like to understand what we overlooked and what
> > information you had that would have allowed us to avoid the current
> issue,
> > as well as why you are planning on leaving the platform.  Thanks...
> >
> > -- Chris
> >
> >
> > On Mon, Aug 6, 2012 at 8:04 AM, Rick Mangi  wrote:
> >>
> >> You could start by being a little more transparent about what you're
> >> doing. Publishing release roadmaps are the norm for almost every
> software
> >> company in the world. You guys seem to love to leave us (the users) in
> the
> >> dark about everything you do until it's released. This is the 2nd time
> our
> >> site has been taken down for days by something which we could have told
> you
> >> was going to break it.
> >>
> >> sorry, but we're bailing on appengine as soon as we can.
> >>
> >>
> >>
> >> On Thursday, August 2, 2012 1:46:14 PM UTC-4, Chris Ramsdale wrote:
> >>>
> >>> Jeff, et al.--
> >>>
> >>> We have verified that a configuration change on our side led to certain
> >>> requests being denied / redirected.  The rollback of this change
> started
> >>> earlier this morning and should be completed shortly.  We are actively
> >>> looking into measures that we can take to ensure that issues like this
> are
> >>> caught prior to rolling out to production.
> >>>
> >>> If your application continues to be impacted please contact me
> directly.
> >>>
> >>> -- Chris
> >>>
> >>> Product Manager, Google App Engine
> >>>
> >>>
> >>> On Wed, Aug 1, 2012 at 11:13 AM, Jeff Schnitzer 
> >>> wrote:
> 
>  Ok, this is fucked up.  Visit http://www.voo.st/, and get this:
> 
>  https://img.skitch.com/20120801-cd1h98pqwb8e8qryct9yjcqwgk.jpg
> 
>  Something is triggering a false positive from a totally undocumented
>  Google security system.  This is really, REALLY not ok.  We are losing
>  sales and looking like total idiots to our customers:
> 
>  -
>  Our systems have detected unusual traffic from your computer network.
>  Please try your request again later. Why did this happen?
> 
>  This page appears when Google automatically detects requests coming
>  from your computer network which appear to be in violation of the
>  Terms of Service. The block will expire shortly after those requests
>  stop.
> 
>  This traffic may have been sent by malicious software, a browser
>  plug-in, or a script that sends automated requests. If you share your
>  network connection, ask your administrator for help — a different
>  computer using the same IP address may be responsible. Learn more
> 
>  Sometimes you may see this page if you are using advanced terms that
>  robots are known to use, or sending requests very quickly.
> 
>  IP address: 208.90.212.26
>  Time: 2012-08-01T18:02:00Z
>  URL: http://www.voo.st/
>  -
> 
>  We use CloudFlare as a reverse proxy.  Wild guess is that some sort of
>  automated security system is cutting in and detecting CF's proxy as an
>  attack.
> 
>  PLEASE TURN THIS OFF NOW.
> 
>  Jeff
> 
>  --
>  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.
>  

[google-appengine] Re: What are the pros and cons of using Google App engine for my startup?

[Alexis]

@Kaan: The limits can be increased as your app grows as long as you make a 
decent use of the resources. The GAE team will make sure your app is able 
to scale and assist you if you become that big (as you will have a Premier 
Account in this case). For instance, some of our apps have the following 
limits: URL Fetch 834,159,222 calls daily, 576,000 calls per minute.

-- 
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/-/NNlXL_4zTZAJ.
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: How to move data reliably from front to backends ?

[Richard]

Yeah, I pretty much figured that firing up backends dynamically would be a 
little slow.  Thank you for testing this option!

I just registered to test/use a Google Compute machine.  I would like to 
test some options on that.  Hopefully they approve me to use it soon.

-R

On Tuesday, August 7, 2012 3:52:01 AM UTC-4, Takashi Matsuo (Google) wrote:
>
>
> Richard,
>
> I've done some experiment with the dynamic backends, and unfortunately I 
> found that it's not suitable for your needs.
> Please feel free to ask again if you have further questions.
>
> -- Takashi
>
>
> On Sun, Aug 5, 2012 at 6:32 AM, Takashi Matsuo  wrote:
>
>>
>> Great to hear that and congrats to your success on Google Play!
>> On Aug 4, 2012 1:40 PM, "Richard"  wrote:
>>
>>> 6 hours of straight coding and testing later, we now have a new backend 
>>> with 10 static B1's acting as a sharded memory proxy for the results.
>>>
>>> We seem to be handling around 900 players with no problems at the moment.
>>>
>>> Special thanks to Takashi for the design & a lot more!
>>>
>>> Time for some much needed sleep.
>>>
>>> On Friday, August 3, 2012 11:18:37 PM UTC-4, Takashi Matsuo (Google) 
>>> wrote:

 Dynamic backend instances automatically scale up/down.
 On Aug 4, 2012 9:21 AM, "Richard"  wrote:

> Hi Takashi,
>
> Yes, I read your post with a theoretical model, but unfortunately, I 
> don't really know how to tell it to scale up/down ?
>
> -R
>
> On Friday, August 3, 2012 6:07:10 PM UTC-4, Takashi Matsuo (Google) 
> wrote:
>>
>>
>> Just wanted to make sure...
>> Have you seen my post about auto-scaling in-memory backends?
>>
>>
>>  -- 
> 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/-/**9Z77HBrZDEYJ
> .
> To post to this group, send email to google-appengine@googlegroups.**
> com .
> To unsubscribe from this group, send email to 
> google-appengine+unsubscribe@**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 view this discussion on the web visit 
>>> https://groups.google.com/d/msg/google-appengine/-/W707lh8eSDwJ.
>>> 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.
>>>
>>
>
>
> -- 
> Takashi Matsuo
>  

-- 
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/-/d-8AnsO28iQJ.
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] Unique Integer ID for a non primary key field for Entities in Google App Engine

[Michael Hermus]

If you use a transaction to retrieve the entity by key (the URL) and then 
create one if it doesn't exist, only one entity should be successfully 
created in the event of a collision. Therefore, even if you create two 
different versions with different unique ids, only one should survive.

On Tuesday, August 7, 2012 8:08:42 AM UTC-4, Neo wrote:
>
> Hi Jeff, 
>
>
> Actually my requirement is that , Whenever I save a new entity, the id 
> field should get autogenerated. If I have to do it on my own (as  you 
> suggested DatastoreService.allocateIds()), how do we handle scenarios like 
> two threads on different machines trying to store the newly created entites 
> in the datastore (thereby trying to assign different ids). I am not well 
> versed with all the concepts. If you can please elaborate, that would be 
> really useful. And you are right in guessing that I need the shortest 
> possible value. Hashes, I suppose are not guaranteed to be unique for two 
> different arbitrary strings.
>
> 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/-/-zhJp8r7laMJ.
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] Task Queue "default"

[Fábio Peruchi]

Hi!

Does anyone know what's the purpose of the "*default*" Task Queue?

Fábio

-- 
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] multiple domains on GAE

[Jeff Schnitzer]

Yes, it should work.  You want to add a wildcard mapping in Google
Apps for Domains.

Jeff

On Tue, Aug 7, 2012 at 7:05 AM, Mehmet Kose  wrote:
> Hi.
> I want to use multiple domains on google app engine, with webapp or
> tornadoweb.
> for example:
>
> the actual url: http://site.com/user/username
>
> I want to show it: http://username.site.com
>
> Is this possible? How do I need to make an configuration.
> thanks a lot.
>
> --
> 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/-/KLnbtuU1MNEJ.
> 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] Unique Integer ID for a non primary key field for Entities in Google App Engine

[Jeff Schnitzer]

Now you have me confused.  I thought you want every URLInfo to have a
unique id?  This is what the allocator will give you.  It generates
unique ids at ferocious rates across an entire cluster of active
machines.

If you somehow want URLInfo objects to share ids, I don't really
understand your business problem.

If you're just looking for a way to ensure that multiple servers don't
create the same URLInfo object at the same time, you need to create
the URLInfo in a transaction that checks for existence of the URLInfo
before writing.

Jeff


On Tue, Aug 7, 2012 at 5:08 AM, Neo  wrote:
>
> Actually my requirement is that , Whenever I save a new entity, the id field
> should get autogenerated. If I have to do it on my own (as  you suggested
> DatastoreService.allocateIds()), how do we handle scenarios like two threads
> on different machines trying to store the newly created entites in the
> datastore (thereby trying to assign different ids). I am not well versed
> with all the concepts. If you can please elaborate, that would be really
> useful. And you are right in guessing that I need the shortest possible
> value. Hashes, I suppose are not guaranteed to be unique for two different
> arbitrary strings.
>
> Thanks,

-- 
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] APP DOWN due to some sort of undocumented Google security system

[Cesium]

Chris,

I am using GAE for my startup and it's just freakin' awesome.

I don't use frameworks. I don't use CDNs (whatever those are!?). I don't 
use SSL.

Just MVP and Objectify, and it flat out rocks.

Daily, I pee in my pants with excitement.

My customers are thrilled. (Both of them).

David
(Thought we needed a little 'balance' on this thread.)

-- 
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/-/f_mKAewJd-cJ.
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] Unique Integer ID for a non primary key field for Entities in Google App Engine

[Ego008]

You can define the Id and use a counter to increase.


http://saepy.sinaapp.com

在 2012-8-7，20:08，Neo  写到：


Hi Jeff,

Actually my requirement is that , Whenever I save a new entity, the  
id field should get autogenerated. If I have to do it on my own (as   
you suggested DatastoreService.allocateIds()), how do we handle  
scenarios like two threads on different machines trying to store the  
newly created entites in the datastore (thereby trying to assign  
different ids). I am not well versed with all the concepts. If you  
can please elaborate, that would be really useful. And you are right  
in guessing that I need the shortest possible value. Hashes, I  
suppose are not guaranteed to be unique for two different arbitrary  
strings.


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/-/sO0eNtmB784J 
.
To post to this group, send email to google- 
appeng...@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com 
.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en 
.


--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To post to this group, send email to google-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] multiple domains on GAE

[Ego008]

Bind usemame.site.com to your app and use URL map in your code.

http://saepy.sinaapp.com

在 2012-8-7，22:05，Mehmet Kose  写到：


Hi.
I want to use multiple domains on google app engine, with webapp or  
tornadoweb.

for example:

the actual url: http://site.com/user/username

I want to show it: http://username.site.com

Is this possible? How do I need to make an configuration.
thanks a lot.
--
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/-/KLnbtuU1MNEJ 
.
To post to this group, send email to google- 
appeng...@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com 
.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en 
.


--
You received this message because you are subscribed to the Google Groups "Google 
App Engine" group.
To post to this group, send email to google-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: numpy and scipy question

[Hans Then]

Hi Anand,

Processing is offline, but the order of magnitude will be more like days 
than 10 minutes, so I guess backends are the way to go. Basically the 
application will perform statistical analysis on large datasets of news 
items and media data. Right now, we run this analysis on hardware we own, 
but we'd like to make the basic toolset available to the scientific 
community. 

As for SciPy being in Fortran, does this mean that there are no plans at 
all to make SciPy available on Appengine? Or only that it will take some 
more time to do so?

Regards,

Hans Then 

Op maandag 23 juli 2012 14:47:19 UTC+2 schreef Anand Mistry het volgende:
>
> If the processing is considered "offline" and not latency sensitive, then 
> you can put that work onto a task queue and take up to 10 minutes. No need 
> for a backend.
>
> As for SciPy, Brandon is exactly right. SciPy is written entirely in 
> Fortran whereas the other third-party libraries we have (NumPy, PIL, lxml) 
> are written in C. For NLTK, do you really need SciPy? According to 
> nltk.org, only NumPy is a dependency (optional).
>
> On Monday, 23 July 2012 09:33:35 UTC+10, Hans Then wrote:
>>
>> Ah. That is very good news. We have no real timing requirements. I think 
>> we will setup a backend instance for long running requests, to get around 
>> the 60s limit.
>>
>> On Mon, Jul 23, 2012 at 1:24 AM, Drake  wrote:
>>
>>> I think we have everything you need.  We are working on some speed 
>>> improvements because unfortunately the 60s limit doesn’t let you work with 
>>> very big documents.
>>>
>>> Do you know how many words at a time you need to put through?
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> *From:* google-appengine@googlegroups.com [mailto:
>>> google-appengine@googlegroups.com] *On Behalf Of *Hans Then
>>> *Sent:* Sunday, July 22, 2012 3:51 PM
>>>
>>> *To:* google-appengine@googlegroups.com
>>> *Subject:* Re: [google-appengine] Re: numpy and scipy question
>>>
>>> ** **
>>>
>>> I am mainly using the classify and the cluster packages.
>>>
>>> ** **
>>>
>>> Thanks for considering this to be included.
>>>
>>> ** **
>>>
>>> Hans 
>>>
>>> Op zondag 22 juli 2012 19:18:25 UTC+2 schreef Brandon Wirtz het volgende:
>>> 
>>>
>>> I am building an API that does much of what NLTK does.  Which parts are 
>>> you looking to use? Likely making API calls to my optimized version would 
>>> cost less than actually running the full version, (which includes a lot of 
>>> things that won’t work on GAE  (like the cool drawing of the sentence 
>>> diagram)
>>>
>>> If the parts you need don’t take too much effort to add, I’ll put them 
>>> on my teams task list for the API release in 2 weeks.
>>>
>>>  
>>>
>>> -Brandon
>>>
>>>  
>>>
>>> *From:* google-appengine@googlegroups.com [mailto:
>>> google-appengine@googlegroups.com] *On Behalf Of *Hans Then
>>> *Sent:* Sunday, July 22, 2012 7:04 AM
>>> *To:* google-appengine@googlegroups.com
>>> *Subject:* Re: [google-appengine] Re: numpy and scipy question
>>>
>>>  
>>>
>>> The application I develop uses libraries such as gensim and NLTK, which 
>>> depend on SciPy. Currently my plan is to run it on Heroku, but I would much 
>>> prefer to use appengine.
>>>
>>>  
>>>
>>> Hans
>>>
>>> On Sun, Jul 22, 2012 at 11:24 AM, Drake  wrote:
>>>
>>> I don’t know then. I thought NumPy was all C… 
>>>
>>> Any how I use Numpy but not SciPy. Apparently Google caters to my every 
>>> whim and so they gave me what I needed.  J
>>>
>>> Depending what you need Matrix.py, and Euclid.py get you many of the 
>>> most common things you would use Numpy and Scipy for.
>>>
>>>  
>>>
>>>  
>>>
>>> *From:* google-appengine@googlegroups.com [mailto:
>>> google-appengine@googlegroups.com] *On Behalf Of *Hans Then
>>> *Sent:* Sunday, July 22, 2012 1:34 AM
>>> *To:* google-appengine@googlegroups.com
>>> *Subject:* Re: [google-appengine] Re: numpy and scipy question
>>>
>>>  
>>>
>>> NumPy is also Fortran. 
>>>
>>>  
>>>
>>> But my confusion is that if SciPy will not be supported, then why 
>>> support NumPy? NumPy and SciPy are hardly ever used separately.
>>>
>>>  
>>>
>>> Hans
>>>
>>> Op zondag 22 juli 2012 09:11:00 UTC+2 schreef Brandon Wirtz het volgende:
>>> 
>>>
>>> SciPy is mostly in Fortran. So I don’t give you good odds.
>>>
>>>  
>>>
>>> *From:* google-appengine@googlegroups.com [mailto:
>>> google-appengine@googlegroups.com] *On Behalf Of *Hans Then
>>> *Sent:* Sunday, July 22, 2012 12:05 AM
>>> *To:* google-appengine@googlegroups.com
>>> *Subject:* [google-appengine] Re: numpy and scipy question
>>>
>>>  
>>>
>>> Hi Anand,
>>>
>>>  
>>>
>>> Are there plans to also support SciPy in the future?
>>>
>>>  
>>>
>>> Hans Then
>>>
>>> Op woensdag 25 januari 2012 00:34:53 UTC+1 schreef Anand Mistry het 
>>> volgende:
>>>
>>> NumPy is available on the Python 2.7 runtime, but SciPy is not.
>>>
>>> -- 
>>> You received this 

[google-appengine] multiple domains on GAE

[Mehmet Kose]

*Hi.*
*I want to use multiple domains on google app engine, with webapp or 
tornadoweb.*
*for example:*
*
*
*the actual url: http://site.com/user/username*
*
*
*I want to show it: http://username.site.com*
*
*
*Is this possible? How do I need to make an configuration.*
*thanks a lot.*

-- 
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/-/KLnbtuU1MNEJ.
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: How to solve the aggregate query with condition in Google App Engine

[Neo]

Hi Joakim,

Thanks for the detailed reply. The problem is, though there will be only a 
single entity for each day, it may have thousands of string > count items. 
I will have to process all these string > count items. If we start 
aggregating each week and each month and so on, and find the largest such 
interval that fits inside the given interval, then we reduce the items 
processing drastically. The only problem remains here is what if there are 
half a million of different input strings between the given interval. It 
seems that even aggregating on months won't be able to help. 

Having said that, I must say that I really like the idea. Do you think that 
it is scalable?

-- 
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/-/2k5o3kCRuSEJ.
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: Under DDoS attack

[Igor]

It's hard to tell if CloudFlare is of any help, I'm still getting a lot of 
hits, only now they all (new ones) come from CloudFlare IPs so I can't 
filter on my own.

Now I turned on most aggressive security setting "I'm under attack!". I 
think this will annoys the hell out of normal users, but if this is the 
only thing that helps, I will have to use this until the attack stops.


On Monday, August 6, 2012 5:38:17 PM UTC+2, Igor wrote:
>
>
> I already looked in to CloudFlare but I was kind of resilient because I'm 
> not quite sure what methods are they using to mitigate DDoS attacks. But I 
> will give it a shot and see what happens.
>
> On Monday, August 6, 2012 5:13:12 PM UTC+2, hyperflame wrote:
>>
>> Try Cloudflare ( they have a free plan, check out 
>> https://www.cloudflare.com/plans 
>> ). They should protect you from some of the DDOS. 
>>
>> On Aug 6, 10:04 am, Mahron  wrote: 
>> > Dynamic blacklisting would be nice. Some kind of service with an 
>> > optimized ip blocker. 
>>
>

-- 
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/-/n400aLbQcTcJ.
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] Unique Integer ID for a non primary key field for Entities in Google App Engine

[Neo]

>
> Hi Jeff, 


Actually my requirement is that , Whenever I save a new entity, the id 
field should get autogenerated. If I have to do it on my own (as  you 
suggested DatastoreService.allocateIds()), how do we handle scenarios like 
two threads on different machines trying to store the newly created entites 
in the datastore (thereby trying to assign different ids). I am not well 
versed with all the concepts. If you can please elaborate, that would be 
really useful. And you are right in guessing that I need the shortest 
possible value. Hashes, I suppose are not guaranteed to be unique for two 
different arbitrary strings.

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/-/sO0eNtmB784J.
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: What are the pros and cons of using Google App engine for my startup?

[alex]

Our experience on py 2.5, 2.7 and Go is a lot different from Java guys.

Pros:
- being able to use Task queues (+ deferred API) and Cron jobs in form of async 
HTTP requests is just awesome.
- I haven't seen anything like Guido's NDB for what concerns async and 
"parallel" execution, plus its caching, autobatching even on url fetches
- LOTs of useful services, which you use via simple APIs
- you totally focus on your app code and not hardware/systems admin. What 
others call AE limitations actually often helps you deliver a better experience 
to your users. Not always but again, in our experience, most of the cases. I 
actually want to thank AE team for imposing some limits (though the real 
reasons of limitations are totally different)
- when something goes wrong you just wait for SRE team to fix it
- nice support for (unit) testing out of the box. Both Go and Python. Actually 
Java too.
- Backends are actually of a great value when you need to "talk to" third 
parties via some API (i.e. not user-facing requests)


Cons:
- some of the services are still a little buggy and their bugfixing is not that 
fast in some cases (e.g. Channels API 400 errors)
- Users API is awesome but unfortunately works with either Google Accounts or 
OpenID. Either way, I'd love to see it supporting OAuth 2.0 and/or "abstract" 
third parties
- I'd love to see a better monitoring system, though I do understand this is a 
complex system to say the least. plus, I think someone mentioned.
- Examples are too simple, e.g. Hello World. So, you'll need to actually figure 
it out yourself. This is not the case with Go land - their examples are closer 
to real world.


Overall we're more than happy with AE. It saved us tons of money so far.

-- alex

PS can't wait for Endpoints API and Compute Engine GA. Unfortunately I didn't 
get into trusted testers (was hoping for Endpoints API)

-- 
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/-/sZkYyDOYppMJ.
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: backend termination question

[jon]

Can Google please respond to this? We also got  Process terminated because 
the backend took too long to shutdown.  on the 17 min 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/-/bTJQ9OLKuxIJ.
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: What are the pros and cons of using Google App engine for my startup?

[Mos]

Perfect summary.  I totally agree to everything.   (Be careful about
statements of Drake; he is trolling around)

On Mon, Aug 6, 2012 at 10:46 AM, Jeff Schnitzer  wrote:

...

> There is plenty to complain about, but GAE is still a good choice.

> There are definitely some downsides to GAE:
>
>  * It's expensive to operate.  An "instance" is significantly more
> expensive and capable of doing significantly less work than what other
> platforms offer.  Your bill starts at $100/mo just to use SSL (and
> with all that private data you certainly are, right?).  In the early
> days you're going to spend more than you would elsewhere... and if you
> have a lot of traffic, you're going to spend a *lot* more.  This is of
> course balanced against not paying for dbas and sysadmins.
>
>  * The concern about lock-in is totally warranted.  If you build a
> complex app on GAE, it's pretty much a total rewrite to go elsewhere.
> The flip side is that you're "locked in" because there are all these
> nice high-level services with great APIs that you would otherwise have
> to invent and manage yourself.
>
>  * Historically, reliability has been spotty.  It pains me to say this
> but things break a lot and you will likely see downtime a lot more
> than if you maintained more of the infrastructure yourself.  GAE is a
> complicated system that is being upgraded on a schedule that is opaque
> to you, plus you're running on shared infrastructure with thousands of
> neighbors who might not be very nice.  And often there's not much you
> can do but scream on this mailing list.  On the plus side, when
> something breaks, someone at Google fixes it - not you.
>
>  * The datastore, while amazing for most web apps, is very challenging
> for some classes of problems.  Two that come to mind are:
>* Heavily transactional systems.  XG transactions help but you
> still have to go through major contortions to build banking-type
> applications.  RDBMSes are clear winners here.
>* Rapidly mutating datasets.  It can be very tricky to work around
> the one-transaction-per-second-per-entity-group throughput limit,
> which gets even slower in XG transactions.  There are usually
> solutions (eg sharding, queueing) but they are all huge PITAs that
> complicate your business logic.  GAE doesn't offer any kind of service
> that fills the niche that Redis fills.
>
>  * There are some downright broken parts of GAE, but they aren't well
> documented as such.  The email service is useless; go with a
> third-party provider instead.  Backends are a disaster; don't use
> them.  This isn't a big deal as long as you know what to expect; keep
> following this mailing list.
>
> Unless you have a "hard problem" for GAE, I'd say go for it and make a
> home here.  The problem is that it's hard to know what a hard problem
> is without already being very familiar with the platform.  Truth be
> told, after three years I still bump into surprises now and then...
> but there's always some solution, even if it involves pushing a
> service fragment out to another cloud provider.  The OP's app sounds
> like a good fit.
>
> Jeff
>
>
> On Sat, Aug 4, 2012 at 1:48 AM, Rerngvit Yanggratoke  
> wrote:
>> As many people have stated about advantages of GAE for startup already, let
>> me provide some disadvantages. The purpose of this is not to discourage
>> people to use GAE but inform them about both sides of the story.
>>
>> The first and most important issue is a vendor lock-in. GAE normally
>> requires you to spend significant efforts to develop and optimize
>> specifically for the platform to run your applications nicely and cost
>> effectively. For example, it is recommended to use a platform-specific
>> database layer like Objectify than the portable but heavy-weight one like
>> JPA or JDO. Another example is that it is recommended to minimize the size
>> of your applications to reduce the cold-start time. This also means that
>> very useful but heavy-weight frameworks like Spring are not going to be
>> comfortable with GAE unless you are willing to pay a steep price of
>> "reserved instances". As a result, if one day you have to move your
>> applications away from GAE to somewhere else, porting your applications is
>> not going to be an easy task. You might have to spend significant resources
>> for that. The possible reason for the movement might be that Google
>> increases the price significantly such that your business model is not
>> sustainable anymore. This happened before to many people. Have a look in the
>> highly popular forum topic
>> (https://groups.google.com/forum/?fromgroups#!topic/google-appengine/obfGjbIkOTI).
>> Now, some people might argue by bringing up Opensource alternative of GAE
>> like Typhoonae (http://code.google.com/p/typhoonae/) or
>> AppScale(http://code.google.com/p/appscale/). Despite the fact those are
>> great and honorable attempts, neither of them are fully compatible with GAE.
>> In other words, if your applications run smooth

Re: [google-appengine] APP DOWN due to some sort of undocumented Google security system

[Jon Stevens]

Sorry, I apologize for the amateur remark, that was a bit much.

jon


On Tuesday, August 7, 2012 12:51:56 AM UTC-7, Jon Stevens wrote:
>
> Chris, 
>
> I've tried to setup billing on my appid three times now. I set it up 
> and then it seems to turn off on its own without even sending me an 
> email or any notification. 
>
> Every few days, I check and it keeps saying that I have a new past due 
> bill. When I go to turn it on again, it asks me for a new shipping 
> address (even though I already have two duplicate addresses in the 
> select box... one was from the last time I tried to set it up and I'm 
> not even shipping anything!?!). 
>
> Now that I'm on the checkout page trying to *pay you money*, I can 
> also see that there is a javascript error on the page, which is 
> preventing any clicks on buttons from working. 
>
> This is seriously the work of amateurs, I really expect more quality 
> and testing from you guys before you put stuff like this into 
> production. Please, let me know when you have billing for my appid 
> fixed. If you can't figure it out, feel free to contact me privately. 
>
> jon 
>
>
> On Mon, Aug 6, 2012 at 4:12 PM, Chris Ramsdale  
> wrote: 
> > Rick, 
> > 
> > We publish upcoming features and functionality within the "App Engine 
> > Features" section of our developer site: 
> > 
> > https://developers.google.com/appengine/docs/features 
> > 
> > In regards to bailing on the platform, it is unfortunate to hear.  If 
> you 
> > have time, I would like to understand what we overlooked and what 
> > information you had that would have allowed us to avoid the current 
> issue, 
> > as well as why you are planning on leaving the platform.  Thanks... 
> > 
> > -- Chris 
> > 
> > 
> > On Mon, Aug 6, 2012 at 8:04 AM, Rick Mangi  wrote: 
> >> 
> >> You could start by being a little more transparent about what you're 
> >> doing. Publishing release roadmaps are the norm for almost every 
> software 
> >> company in the world. You guys seem to love to leave us (the users) in 
> the 
> >> dark about everything you do until it's released. This is the 2nd time 
> our 
> >> site has been taken down for days by something which we could have told 
> you 
> >> was going to break it. 
> >> 
> >> sorry, but we're bailing on appengine as soon as we can. 
> >> 
> >> 
> >> 
> >> On Thursday, August 2, 2012 1:46:14 PM UTC-4, Chris Ramsdale wrote: 
> >>> 
> >>> Jeff, et al.-- 
> >>> 
> >>> We have verified that a configuration change on our side led to 
> certain 
> >>> requests being denied / redirected.  The rollback of this change 
> started 
> >>> earlier this morning and should be completed shortly.  We are actively 
> >>> looking into measures that we can take to ensure that issues like this 
> are 
> >>> caught prior to rolling out to production. 
> >>> 
> >>> If your application continues to be impacted please contact me 
> directly. 
> >>> 
> >>> -- Chris 
> >>> 
> >>> Product Manager, Google App Engine 
> >>> 
> >>> 
> >>> On Wed, Aug 1, 2012 at 11:13 AM, Jeff Schnitzer  
> >>> wrote: 
>  
>  Ok, this is fucked up.  Visit http://www.voo.st/, and get this: 
>  
>  https://img.skitch.com/20120801-cd1h98pqwb8e8qryct9yjcqwgk.jpg 
>  
>  Something is triggering a false positive from a totally undocumented 
>  Google security system.  This is really, REALLY not ok.  We are 
> losing 
>  sales and looking like total idiots to our customers: 
>  
>  - 
>  Our systems have detected unusual traffic from your computer network. 
>  Please try your request again later. Why did this happen? 
>  
>  This page appears when Google automatically detects requests coming 
>  from your computer network which appear to be in violation of the 
>  Terms of Service. The block will expire shortly after those requests 
>  stop. 
>  
>  This traffic may have been sent by malicious software, a browser 
>  plug-in, or a script that sends automated requests. If you share your 
>  network connection, ask your administrator for help — a different 
>  computer using the same IP address may be responsible. Learn more 
>  
>  Sometimes you may see this page if you are using advanced terms that 
>  robots are known to use, or sending requests very quickly. 
>  
>  IP address: 208.90.212.26 
>  Time: 2012-08-01T18:02:00Z 
>  URL: http://www.voo.st/ 
>  - 
>  
>  We use CloudFlare as a reverse proxy.  Wild guess is that some sort 
> of 
>  automated security system is cutting in and detecting CF's proxy as 
> an 
>  attack. 
>  
>  PLEASE TURN THIS OFF NOW. 
>  
>  Jeff 
>  
>  -- 
>  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+unsubsc

[google-appengine] Re: What are the pros and cons of using Google App engine for my startup?

[Tomas]

My two cents (as a Java dev):

Pros:

- it's not complicated, you can do easy things in easy way (well maybe the 
Database can be tricky when you come from SQL world :-)
- very easy and fast start of development (if you use simple stack as 
servlet + jsp + objectify)
- for small projects its basically free
- very easy deployment
- very easy use of messaging as all is basically just async http request
- it scales automatically
- you don't need admin for db/app server and other stuff

Cons:

- you can't use usual frameworks aka Spring -> which means you spent a lot 
of time implementing basic features which are included in your framework 
(ie. Authentication, MVC, templating, Caching and so on) - I mean you can 
probably work it around and use some subset of frameworks or libraries but 
my experience tells me you will keep trying to find some hacks and 
workarounds instead focusing on real development and adding features (For 
example with spring you add @Cacheable annotations to method which will 
automatically use in-memory cache + propagate to memcache through ehcache 
(yes one line settings) - on GAE you will need to write it by yourself)
- you don't have control over resources - when GAE a has bad day you can't 
do anything with it and you can just watch how it spins instances or fails 
when talk to db - and you usually don't get a word from google what is 
actually happening
- it doesnt fit all type of projects - for example in my app I have a web 
front and then a backend business which was processing multi-threaded 
requests while was user browsing pages - the backend was done through tasks 
and it was killing the instance so I had to move that logic to AWS where it 
runs on micro instance with 0.1 load all the time very nicely (this was 
before google announced backends) - my frontend client facing app still 
runs on GAE and I haven't touched it for more than year and didn't have 
much issues even if its sits in MS datastore :)
- it can be expensive (you need to optimize sooner) - I was usually 
optimizing after getting more hits and so but on GAE you sometime needs to 
optimize in advance because it just consumes a lot of resources (ie. 
reads/writes/indexes to db)
- something is just not going to work at all and you will need to find 
alternative (ie. reading from local drive etc)

On Friday, 3 August 2012 21:37:36 UTC+12, Levi Campbell wrote:
>
> I'm building a startup, and I'm considering GAE as the platform, however 
> I've been having a hard time finding information on why a startup might 
> consider GAE instead of the many cloud providers out there. Let me explain 
> what I'm working on.
>
> I'm a big fan of David Allen's Getting Things Done: The Art of 
> Stress-Free 
> Productivity,
>  
> and after trying several tools and online services that (claim to) 
> implement the GTD methodology, I couldn't find anything that I loved, so I 
> decided to build my own and make it available as a SaaS offering. This app 
> will allow users to pull in their info_crap from email, facebook, twitter 
> (and yes, I do have plans to add support for more social networks.), and 
> RSS feeds and organize it by relationship to the sender (i.e. family, 
> work colleague, vendor, and the like), project (i.e. planning a family 
> vacation.), and context (Either the when or where something should 
> happen.).\
>
> Would GAE be a good fit for the application I'm developing? Why?
>
>

-- 
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/-/ZEN0vvWzcUQJ.
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] APP DOWN due to some sort of undocumented Google security system

[Jon Stevens]

Chris,

I've tried to setup billing on my appid three times now. I set it up
and then it seems to turn off on its own without even sending me an
email or any notification.

Every few days, I check and it keeps saying that I have a new past due
bill. When I go to turn it on again, it asks me for a new shipping
address (even though I already have two duplicate addresses in the
select box... one was from the last time I tried to set it up and I'm
not even shipping anything!?!).

Now that I'm on the checkout page trying to *pay you money*, I can
also see that there is a javascript error on the page, which is
preventing any clicks on buttons from working.

This is seriously the work of amateurs, I really expect more quality
and testing from you guys before you put stuff like this into
production. Please, let me know when you have billing for my appid
fixed. If you can't figure it out, feel free to contact me privately.

jon


On Mon, Aug 6, 2012 at 4:12 PM, Chris Ramsdale  wrote:
> Rick,
>
> We publish upcoming features and functionality within the "App Engine
> Features" section of our developer site:
>
> https://developers.google.com/appengine/docs/features
>
> In regards to bailing on the platform, it is unfortunate to hear.  If you
> have time, I would like to understand what we overlooked and what
> information you had that would have allowed us to avoid the current issue,
> as well as why you are planning on leaving the platform.  Thanks...
>
> -- Chris
>
>
> On Mon, Aug 6, 2012 at 8:04 AM, Rick Mangi  wrote:
>>
>> You could start by being a little more transparent about what you're
>> doing. Publishing release roadmaps are the norm for almost every software
>> company in the world. You guys seem to love to leave us (the users) in the
>> dark about everything you do until it's released. This is the 2nd time our
>> site has been taken down for days by something which we could have told you
>> was going to break it.
>>
>> sorry, but we're bailing on appengine as soon as we can.
>>
>>
>>
>> On Thursday, August 2, 2012 1:46:14 PM UTC-4, Chris Ramsdale wrote:
>>>
>>> Jeff, et al.--
>>>
>>> We have verified that a configuration change on our side led to certain
>>> requests being denied / redirected.  The rollback of this change started
>>> earlier this morning and should be completed shortly.  We are actively
>>> looking into measures that we can take to ensure that issues like this are
>>> caught prior to rolling out to production.
>>>
>>> If your application continues to be impacted please contact me directly.
>>>
>>> -- Chris
>>>
>>> Product Manager, Google App Engine
>>>
>>>
>>> On Wed, Aug 1, 2012 at 11:13 AM, Jeff Schnitzer 
>>> wrote:

 Ok, this is fucked up.  Visit http://www.voo.st/, and get this:

 https://img.skitch.com/20120801-cd1h98pqwb8e8qryct9yjcqwgk.jpg

 Something is triggering a false positive from a totally undocumented
 Google security system.  This is really, REALLY not ok.  We are losing
 sales and looking like total idiots to our customers:

 -
 Our systems have detected unusual traffic from your computer network.
 Please try your request again later. Why did this happen?

 This page appears when Google automatically detects requests coming
 from your computer network which appear to be in violation of the
 Terms of Service. The block will expire shortly after those requests
 stop.

 This traffic may have been sent by malicious software, a browser
 plug-in, or a script that sends automated requests. If you share your
 network connection, ask your administrator for help — a different
 computer using the same IP address may be responsible. Learn more

 Sometimes you may see this page if you are using advanced terms that
 robots are known to use, or sending requests very quickly.

 IP address: 208.90.212.26
 Time: 2012-08-01T18:02:00Z
 URL: http://www.voo.st/
 -

 We use CloudFlare as a reverse proxy.  Wild guess is that some sort of
 automated security system is cutting in and detecting CF's proxy as an
 attack.

 PLEASE TURN THIS OFF NOW.

 Jeff

 --
 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 view this discussion on the web visit
>> https://groups.google.com/d/msg/google-appengine/-/2xbF2m-Q5a0J.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@

Re: [google-appengine] Re: How to move data reliably from front to backends ?

[Takashi Matsuo]

Richard,

I've done some experiment with the dynamic backends, and unfortunately I
found that it's not suitable for your needs.
Please feel free to ask again if you have further questions.

-- Takashi


On Sun, Aug 5, 2012 at 6:32 AM, Takashi Matsuo  wrote:

>
> Great to hear that and congrats to your success on Google Play!
> On Aug 4, 2012 1:40 PM, "Richard"  wrote:
>
>> 6 hours of straight coding and testing later, we now have a new backend
>> with 10 static B1's acting as a sharded memory proxy for the results.
>>
>> We seem to be handling around 900 players with no problems at the moment.
>>
>> Special thanks to Takashi for the design & a lot more!
>>
>> Time for some much needed sleep.
>>
>> On Friday, August 3, 2012 11:18:37 PM UTC-4, Takashi Matsuo (Google)
>> wrote:
>>>
>>> Dynamic backend instances automatically scale up/down.
>>> On Aug 4, 2012 9:21 AM, "Richard"  wrote:
>>>
 Hi Takashi,

 Yes, I read your post with a theoretical model, but unfortunately, I
 don't really know how to tell it to scale up/down ?

 -R

 On Friday, August 3, 2012 6:07:10 PM UTC-4, Takashi Matsuo (Google)
 wrote:
>
>
> Just wanted to make sure...
> Have you seen my post about auto-scaling in-memory backends?
>
>
>  --
 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/-/**9Z77HBrZDEYJ
 .
 To post to this group, send email to google-appengine@googlegroups.**
 com .
 To unsubscribe from this group, send email to
 google-appengine+unsubscribe@**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 view this discussion on the web visit
>> https://groups.google.com/d/msg/google-appengine/-/W707lh8eSDwJ.
>> 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.
>>
>


-- 
Takashi Matsuo

-- 
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: What are the pros and cons of using Google App engine for my startup?

[André Pankraz]

Hi,

I have read many pros...some quite extensive and without any Con at all. I 
like the app engine idea, but really, that is a bit one-sided.

Huge pros: Architecture with scalability in mind, dynamic scaling / 
pricing, easy to setup, lots of nice services like mail, messaging etc., 
HA/backup Other people have already shown them.

Huge cons (for me):

   - Really expensive...what benefit has (theoretically) endless 
   scalability if i'm instant bankrupt with a DoS. AWS continuously lowers 
   prices, GAE not so much. If I restrict quota to reasonable financial 
   amounts I'm often not better than 2 or 4 high end root servers. I need 
   _dozens_ of GAE instances to match the speed of 2-4 dedicated good servers, 
   don't know why. The database operations are also expensive.
   - Severe restrictions on useable proven frameworks, developing for GAE 
   is very time consuming and expensive because of this and because I have to 
   optimize a lot. Many peope claim how expensive this admin is that I don't 
   need anymore with GAE, but I don't believe this story. You need multiple 
   times more money to develop for GAE than for this admin guy. In a startup 
   you can also setup your system by yourselfes, really some guys here are 
   talking like setting up a clustered tomcat/jboss with network/monitoring 
   stuff and a database is rocket since...with todeys tools it's not - and I'm 
   free to choose between something like PostgreSQL and Neo4j, Cassdandra or 
   whatever.
   - Unstable platform and bugs in services. You are fully dependant of 
   Google with this. If they decide to update to e.g. JRE 7 than you can use 
   JRE 7 Bytecode, not before. If they decide to update to JRE 7 than you must 
   use it...this may introduce incompatibility issues with your untouched 
   deployments. Same for services. Services have bugs, e.g. upload of empty 
   Blobs created empty BlobInfo, no Messages from Backends to User, Appstats 
   for Backends doesn't work in development, no Blobinfo Hashvalue was created 
   for development mode etc. - all this costs much time and you cannot fix 
   this or use another library without much effort.

There are more Pros and Cons, was my list,

Yes Brandon, I do it all wrong, TIA.

Regards,
André

-- 
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/-/4SDLYd06ytsJ.
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.