If my recollection of the architecture is correct, the edge servers that do the https work are not the same as the application servers where you are racking up CPU charges.
Therefore you are probably going to get the https heavy lifting and bandwidth for the same price as non-https. On Mon, Jan 24, 2011 at 11:05 AM, Dave Peck <[email protected]> wrote: > Does using HTTPS imply higher CPU cost? Or is the hard work done > outside of metering? > > (Also, the documentation about secure quotas seems a little vague. My > impression is: at least up front, they're the same as the non-secure > quotas, and "secure bandwidth" costs the same as regular?) > > Thanks, > Dave > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- -- A. Stevko =========== "If everything seems under control, you're just not going fast enough." M. Andretti -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
