Yes, I was thinking of heightened limit in certain situations / feedback based improvement etc. -- decided to revise things now
I went with CloudFlare - at least until it doesn't work out - the risk is probably ~ 2 hour downtime at max. during switch from CloudFlare services to custom dns/ssl, not much of a risk Experience: - Really fast and fun integration - 30 minutes max. - Easy work-around using Page Rules for AppEngine's naked domain issue, you can redirect naked.com/* to https://www.naked/com/$1 - Really simple SSL - just works - Simple DNS - Gives a confident vibe - might be even a con - if it doesn't work out - it would be hard to match CloudFlare's simple functions On Wednesday, August 21, 2013 12:41:53 AM UTC+3, Joshua Smith wrote: > > > On Aug 20, 2013, at 5:29 PM, Kaan Soral <[email protected] <javascript:>> > wrote: > > in real life, I'm not sure whether there are scenarios, where a > high-number of people share the same IP address and use a service/app > > > There are many such scenarios. > > Any place lots of people get free wifi (stadiums, airports, etc.) this > will happen. > > Also, most large corporate internet access is proxied through a very small > number of concentrators. > > -Joshua > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
