Yes, that's what it means.
Hopefully any https latency is minimal, at least for apis where you
don't have to drag every subsidiary resource in via https too. Use
HTTP keep alives; all overhead is on initial connection.
On Saturday, January 30, 2010, rob ganly wrote:
> hi david,
> from what i ga
hi david,
from what i gather it is stating not that you MUST use plaintext over HTTPS
but that if you are using plaintext then you should ONLY do so over HTTPS.
>> and PLAINTEXT only for secure (HTTPS) requests.
i agree that it isn't entirely clear in the documentation, but that's what i
*think*
Currently I'm using HMAC-SHA1 over HTTP and have been considering
adding in SSL to my app, but am slightly confused as to what is more
appropriate. Obviously I'll be losing a *lot* of speed with SSL, and
from reading the specification I'm unclear whether it's actually
necessary. For example:
http:
