Privacy and integrity of web-mobile-interactions: App Engine, HTTP/2 or SPDY.

Everyday several alternatives develop and mature as many are in the experimental phases when it comes to protect the privacy and integrity of web interactions.

Challenges are exceptional and stakes are in the core of our living and working conditions.

The emerging implemented SPDY protocol, in addition to optimization and server-push features, automatically supports TLS and persistent connections.

The new HTTP/2 protocol applies and further improves upon all the learnings from SPDY, including the features that make batching secure requests a breeze.

Henceforth App Engine automatically uses HTTP/2 or SPDY for all HTTPS traffic, as long as the client also supports either protocol.

Connectikpeople.co also recall that, as a mobile-app developer, in order to take advantage of HTTP/2 or SPDY to batch HTTPS REST requests to your App Engine app, you may need to code and build your app using a library that supports one or both of these protocols.

Meaning that, for Android, you can try Square’s OkHttp library. On iOS, SPDY is enabled by default; however, Twitter’s CocoaSPDY library is a popular option.