ompatible clients to flush out of the ecosystem. The
alternative is to support SNI and pollute the web with certificate warnings
when Android and Blackberry clients visit certain GAE sites. I don't think
anybody wants this and I hope Google does the right thing.
- Doug Anderson
On Sund
>
> Thanks for the update Cayden... it's nice to know this issue is still
> alive and high priority!
>
> For me the biggest issue with SNI is pre-ICS Android and Blackberry more
> than IE (or Safari) with Windows-XP. I can appreciate the desire and
> temptation for an SNI solution but the r
ompatible clients to flush out of the ecosystem. The
alternative is to support SNI and pollute the web with certificate warnings
when Android and Blackberry clients visit certain GAE sites. I don't think
anybody wants this and I hope Google does the right thing.
- Doug Anderson
>
&g
I share your sentiment about the SSL support 100%... it's great to finally
have it but the reality is the ecosystem just isn't ready for SNI yet.
There are still too many browsers that don't support SNI including the
Kindle Fire and every other pre-Ice Cream Sandwich Android device (of which
t
I use mailgun with GAE... it works with local development environment and
deployed production environment. Their support is awesome and the web
service is lightning fast. I moved to mailgun because my app requires more
flexibility than what the native GAE email capabilities provide
(specifica
Have you tried increasing the bucket_size above the default value of 5
and/or the processing rate above 5/s? I'm not saying there isn't a bug...
I'm just curious if there's a workaround or if perhaps the problem is
triggered by exceeding some threshold from which task queue manager never
prope
Can you also please fix issue 5236 since files.blobstore.create() still
fails 1-2% of the time due to timeout (it hangs in google coded as
explained in issue)?
https://code.google.com/p/googleappengine/issues/detail?id=5236
On Tuesday, March 5, 2013 9:38:10 PM UTC-5, Ryan Huebsch wrote:
>
> We'v
Could you please clarify this point?
- The Experimental Files API has been deprecated in favor of the Google
Cloud
Storage library, now available as a Preview feature.
Does this mean Blobstore writes are deprecated (I assume so)?
Does it also mean the current Cloud Storage "files" based API is
Thanks for the clarification Chris. FWIW the blobstore files API (at least
in Python) is also not very reliable (I've seen hangs as often as 1 in 10
file create-writes). So I'll be migrating my blob writes from blobstore to
GCS as soon as possible!
>From my perspective the blobstore could be
Below is a tested python example showing how to write a JPEG to both GCS
using the "new" API and Blobstore. Note how VERY similar the process is
(all things considered). IMO Google did a terrific job making this
inevitable transition mostly seamless. The only possible prerequisite
setup requ
... the "gcs_file.close()" line is not needed (I forgot to remove it when I
changed to use the "with" statement)
On Tuesday, June 4, 2013 2:46:22 PM UTC-4, Richmond Manzana wrote:
>
> Hello Again Everyone!
>
> We've been busy since I/O!
>
> Pre-release SDKs for Python and Java here:
> http://code
yep... a risk I'm willing to live with... but you could increase the file
name length, increase the set of GCS_NAME_CHARS, and/or add exception
handling if it's a concern for you... just remember the max GCS objectname
length is 1024 bytes of UTF-8 encoded chars.
On Tuesday, June 11, 2013 6:21:
Please consider adding jinja 2.7 to the python SDK and live runtime
environment. Thanks.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+
1. Why hasn't the GCS client download been updated since early June?
Numerous changes have been checked in since then. As I understand it one
of them is crucial to GCS reliability.
2. Why hasn't the GCS client been integrated into the App Engine SDK /
Runtime. This seems l
I realize this is likely a GCS server issue and I don't mean to distact
from that but I'd also like to point out that the SDK's
google-api-python-client (which I assume GCS relies upon under the hood) is
v1.0beta6 from Oct 28, 2011, where the latest release seems to be v1.2 from
Aug 7, 2013. I
FWIW... I'd like to add my voice in support of a high priority for this
capability. Now that we have SSL... improved domain management is at the
top of my wish list. On the email front... I use Mailgun with App Engine
precisely because I need more flexibility than GAE's native email provides.
My biggest gripe about GAE pricing is the $39/month for VIP SSL. If you
want a custom domain and aren't yet ready to make the SNI leap then you
have a $39/month floor just because you want a secure site. I think GAE
has us surrounded with enough other pricing boxes that they don't need to
ext
I started getting GCS client errors with 1.8.8 win dev server (code
previously working). Upgrading to the latest GCS client code (r127) fixed
my problem.
https://code.google.com/p/appengine-gcs-client/downloads/list
On Monday, October 7, 2013 10:29:01 AM UTC-4, Francois Masurel wrote:
>
> Hi
My advice would be to use Stripe.com for processing payments. You'll be
amazed at how easy it is to get started AND customers don't have to leave
your site!
(I'm not associated with Stripe in any way... just using it with App Engine
and can attest to its ease of use)
I may re-add PayPal at som
stripe from US/UK/Ireland - as far as I
> remember
>
> On Saturday, January 4, 2014 9:51:13 PM UTC+2, Doug Anderson wrote:
>>
>> My advice would be to use Stripe.com for processing payments. You'll be
>> amazed at how easy it is to get started AND customers don'
le providers etc
>
> (Paypal/Braintree acquisition was alarming, I hope they don't mess
> braintree too :)
>
> A beautiful reference for anyone who are interested:
> https://spreedly.com/gateways
>
> On Monday, January 6, 2014 10:16:56 PM UTC+2, Doug Anderson wrote
Here's how I did it:
1. Login to admin.google.com with your Google Apps user/pwd for the
domain
2. From the Google Apps "Admin Console"
3. More Controls - Security - Show more - SSL for Custom Domains
4. You'll then see a form field to enter your App Engine application id
and p
please and thank you)
>
> Regards,
> Troy
>
> On Tuesday, 14 January 2014 14:43:25 UTC-5, Doug Anderson wrote:
>>
>> Here's how I did it:
>>
>>1. Login to admin.google.com with your Google Apps user/pwd for the
>>domain
>>2. From the Goo
Rafael & Kaan... since you both utilize dynamic image serving, do either of
you have an issue concerning the size of dynamically served images? I
filed the issue below a while ago and it has seemingly been ignored by
Google. In short my grievance is that dynamically served images are
effectiv
ge serving, I
> control all the parameters and can also add things like watermarking,
> vertical cropping and WEBP formatting.
>
> thanks
> rafa
>
>
> On Wed, Jan 22, 2014 at 12:57 PM, Doug Anderson
>
> > wrote:
>
>> Rafael & Kaan... since you both
make sense if you
> have your server bills are in the thousands and are struggling with server
> costs.
> If you're an early stage startup with < $100 bill or an overfunded startup
> or a big corporation, who cares? :)
>
> thanks
> rafa
>
>
> On Wed, Ja
Yep... I filed this in June 2013... one would think it would be a fairly
straightforward integration... from the outside it feels like Google needs
another engineer dedicated to GAE Python. At the time there were other
pieces of code that were also out of sync with the latest (release) builds
I've been using PyCharm and am very pleased with it. I've also used
JetBrains' WebStorm with node.js projects and was quite pleased with that
as well.
On Sunday, March 2, 2014 6:49:14 PM UTC-5, Cezary Wagner wrote:
>
> Thanks for hints - it is not helpful.
>
> Discussion is very old and there i
+1 I've always said SSL on GAE should be free... Google should encourage
secure connections. App Engine has us surrounded with enough other toll
booths that charging for SSL seems completely unnecessary. It sets the
baseline cost artificially high for apps that want to use a custom domain
(I
Is App Engine's SSL protected from the OpenSSL heartbleed bug? Since a
Google Engineer discovered the bug I figure there's a good chance App
Engine has the patch. ???
http://heartbleed.com/
https://www.openssl.org/news/secadv_20140407.txt
--
You received this message because you are subscribe
going through ???.appspot.com appears to be clean (not vulnerable to
heartbleed)... still not sure about custom domains.
On Tuesday, April 8, 2014 10:19:49 AM UTC-4, Doug Anderson wrote:
>
> Is App Engine's SSL protected from the OpenSSL heartbleed bug? Since a
> Google Engineer
If the Admin Console would add support for editing repeated fields I'd be a
happy camper. That's the primary reason I have to do custom admin pages.
I've also implemented my own bulk upload for HRD... my implementation
isn't terribly generic though.
On Saturday, June 7, 2014 5:02:35 PM UTC-4,
Having recently significantly exceeded the 200 index limit... I began
trying to figure out what GAE actually supports in a desperate attempt to
get back under the limit. You'd think the documentation would make this
clear and maybe it does for bigger brains than mine. But for me some of
the o
rgae
I hope you find it useful!
- Doug Anderson
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To
You need to go through Apps BUT you don't need to go through Apps
separately for each domain. AFAIK you only need to have a separate Google
Apps account for each domain *if* you need to map the naked domain of each.
Otherwise create a single Apps account and at admin.google.com:
1. More Contr
I hadn't heard about Google Domains until I read it here... it does look
very promising... I would also consider moving away from GoDaddy. I found
this particularly encouraging... (I imagine comparable App Engine support
for paid Apps is more difficult to implement???)
Support
With Google Doma
I wanted to share my recent partial success with naked domains... with the
new cloud console "Custom Domains" you can map your naked non-SSL domain to
your app. After doing that... I detect the naked domain as part of my
'require SSL' logic in the App and redirect to https://www.mydomain.com.
I've been wondering for a while if the 2.0.0 release would be anything
particularly special or just another incremental bump from 1.9.9? :) I'm
guessing the later since all seems relatively normal on the eve of the bump.
+1 to announcing here though
On Tuesday, August 19, 2014 1:34:18 PM UTC-4
As Vinny and others have said... use Google Cloud Storage and dynamic image
serving.
BUT please also star this issue:
https://code.google.com/p/googleappengine/issues/detail?id=9979
To make a long story short... when the dynamic image serving service
resizes a jpeg image it effectively uses a
I assume you fixed it or the DNS had time to propagate because your naked
domain works for me.
On Monday, August 25, 2014 10:24:14 AM UTC-4, cahit coşkun wrote:
>
> Hi,
> I tried to configure a naked domain for my application with the
> instructions from
> https://developers.google.com/appengin
My recommendation would be one of the following for bronze customers:
1. Give bronze customers 1 (non-billing) support ticket per month
2. Give bronze customers N tickets per year
3. Give bronze customers 1 ticket for every X dollars spent on services
(1 ticket per $150 spent on servi
Just curious... do you have billing enabled? The free quota limits are
pretty low last I checked (100/day complex, 1000/day simple). I'm pretty
sure there are no query limits if billing is enabled... I'm working on more
heavily adopting the search API and I'm interested in any issues people
My CC renewed in June (same card #, different CVC, updated expiration,
etc.)... I received the following email from Google Billing and all worked
out perfectly (I was actually quite impressed with the level of
integration):
We're updating your bank account details.
Hello from Google,
We'l
I've certainly felt that App Engine hasn't been a significant priority for
Google for quite some time. Legitimate bug reports can go unacknowledged
for years. The velocity of change has been largely centered around
increased language support rather than significant service expansion and/or
bu
I don't think there's any reason to migrate existing apps unless App Engine
no longer satisfies your requirements. I don't see App Engine going
away... you just need to set your expectations of the platform accordingly
(don't expect bugs to get resolved unless you have a paid support plan,
don
+1 nice to hear from Dan... very encouraging indeed!!!
+1 to PKs comments as well...
Hopefully Dan's improvement list includes better Datastore admin...
especially the ability to edit repeated fields! I have to write custom
admin code for every repeated field I may need to edit. The strategic
FWIW I'm facing the same problem and I'm reasonably certain the issue is
simply a limitation of the BlobstoreUploadHandler. The handler stores
uploaded blobs perfectly fine and gives your handler the BlobInfo for each
blob BUT it seems to discard any non file (type='file') form fields. So if
I have to retract my previous post... this does appear to be working
for me. I can use "self.request.get('description')" to retrieve the
text description form field. My previous problem was that
name='descripton' was spelled wrong in my html form (missing the last
'i')... doh!
I think your issue
48 matches
Mail list logo
