Faster Web with HTTP/2

11 May 2016 Sergio Santoro

4 minute read

HTTP is the protocol that powers the Web. It was originally designed in 1996 for transferring and manipulating simple text-based documents (mainly hypertext resources). Nowadays it’s been adopted for many different purposes. It’s used for: multimedia content transfer, rich real-time session-based web applications, API messages dispatch, Internet of Things and much more. For this reason, the HTTP specifications are continuously updated, by adding new features and improving performance.

In May 2015, the latest version 2.0 was standardized with RFC 7540. This introduced major differences on how the low-level protocol works. From the application perspective, very little has changed: requests, responses, resources, headers and HTTP methods are still there. New features have been added such as the possibility to push resources to the client.

WAMP, Web Application Messaging Protocol.. e PHP!

28 September 2015 Luca Boeri

5 minute read

Dalle notifiche di Facebook ad un tweet stream, da Google Docs ai giochi multiplayer in HTML5, la necessità di uno scambio dati in due direzioni, efficiente e a bassa latenza, ha determinato l’ascesa negli ultimi anni di soluzioni basate su WebSocket .

Internet delle cose e web 2.0 trovano oramai sempre meno spazio all’interno del protocollo HTTP/1. Le tecniche di polling e long polling, in voga fino a pochi anni fa, non permettevano di trasmettere in full duplex (tra server e client) contemporaneamente, erano costrette ad un alto overhead HTTP e richiedevano diversi sforzi per simulare notifiche push server side.