In modern web applications, it’s a common pattern to serve the web API and the frontend app from different subdomains: https://api.example.com: your web API, usually serving JSON documents https://example.com: your web application, usually built in JavaScript, generating HTML documents from the raw JSON data retrieved from the API This was the pattern implemented by API…
Category: Go
Webperf: PHP after Server Push
Here are the slide deck from the talk I gave this morning for AFUP Day 2021! And here is the video (in French): Google recently announced that it will remove Server Push support from its flagship browser. Server Push is a technology that is part of the HTTP/2 and HTTP/3 standards. Server Push is designed…
Using the “103 Early Hints” Status Code in Go Applications
103 is a new experimental HTTP status code defined in RFC 8297. It’s an informational status that can be sent by a server before the main HTTP response. Used in conjunction with the Link HTTP header and the preload relation, 103 gives the client the opportunity to fetch resources (assets, images, related API documents…) related…
The Mercure.rocks Hub is now based on Caddy Web Server
I’m very happy to announce the immediate availability of the Mercure.rocks Hub version 0.11! The Mercure.rocks Hub is a free software implementing the Mercure specification, an open protocol for fast, reliable and battery-efficient in-browser real-time communications. Version 0.11 is a major milestone for the project! As you may know, the Mercure.rocks Hub is written in…
A Structured HTTP Fields Parser and Serializer for the Go Programming Language
“Structured Field Values for HTTP” is an upcoming RFC defining a set of well-defined data types to use in HTTP headers and trailers. This new format will improve the interoperability and the safety of HTTP by allowing to create generic parsers and serializers suitable for all HTTP headers (currently, most headers need a custom parser)…
Say Hello to Mercure 0.10!
I’m very excited to announce the immediate availability of the version 6 of the Mercure Internet Draft as well as of the version 0.10 of the reference implementation! Mercure is a real-time protocol built on top of Server-sent Events and leveraging HTTP/2+. It allows to push messages to JavaScript webapps, mobile apps or IoT devices…
Vulcain: HTTP/2 Server Push and the rise of client-driven REST APIs
Watch a longer video (English)!Watch a French version. Over the years, several formats have been created to fix performance bottlenecks of web APIs: the n+1 problem, over fetching, under fetching… The current hipster solution for these problems is to replace the conceptual model of HTTP (resource-oriented), by the one of GraphQL. It’s a smart network…
Mercure – Real-Time for PHP Made Easy (Forum PHP)
Yesterday at Forum PHP 2019 I presented how easy it is to create real-time apps using PHP (among other languages) and the Mercure protocol. I also introduced the shiny and new Mercure website (designed by Laury S.)! A special thanks to Eric Comellas who jumped on stage to explain how iGraal uses Mercure on a…
Upcoming conferences: AFUP Day, Web2Day, API Platform Meetup and more!
During the spring I’ll speak at several tech events about my projects Mercure (Go), API Platform (PHP, server-side and JS, client-side) and Symfony Panther (PHP/WebDriver): AFUP Day, May 17th in Lille Discover Symfony Panther, a brand new end-to-end testing tool using real web browsers for Symfony and PHP. API Platform pre-Web2day meetup, June 3th in…
Stack2Slack: a Slack bot written in Go to monitor StackOverflow tags
At Les-Tilleuls.coop, we use Slack to centralize our communications and notifications. And, as the maintainers of the API Platform framework, we also do our best to help the community on StackOverflow when we have some free time. Until recently we were just checking periodically the StackOverflow website for new questions. But because all our notifications (GitHub,…