PUBLIC MARKS with tag http

help me to share books locally without hassle with friends, books fans or neighbours. I created Forban to share files easily on the local network. The software is a first implementation of the Forban protocols : fully relying on traditional HTTP with a simple UDP protocol for broadcasting and announcing the service on the local network.

http_rrd_profiler is an HTTP testing/monitoring tool written in Python. It uses Python's httplib to send a GET request to a web resource and adds performance timing instrumentation between each step of the request/response. RRDTool is used for data storage and graph generation. RRDtool is an open source, high performance logging and graphing system for time-series data.

Monarch is a set of libraries and tools for creating high-performance REST-based, native JSON Web Services. Monarch is best suited for sites that rely on thousands of AJAX calls per minute to provide their core functionality. For more information on Monarch performance, check out the blog posts at Digital Bazaar.

VertexDB is a high performance graph database server that supports automatic garbage collection. It uses the HTTP protocol for requests and JSON for it's response data format and the API is inspired by the FUSE filesystem API plus a few extra methods for queries and queues. It's implementation is currently built on top of TokyoCabinet and libevent.

# Use Accept-Language – it just works

# Use IP detection as a fallback for language, or a separate test to determine jurisdiction

# Cookie your visitors’ language preferences, so you are consistent

# Provide a simple way to switch language, everywhere

# Treat language and compliance issues as two entirely separate problems

Vous connaissez HTTP, un peu, beaucoup, à la folie ? Mais êtes vous sûrs d’avoir tout saisi ? Cette présentation vous donnera quelques pistes pour comprendre la métaphore HTTP et son utilisation réelle (et limitée) sur le Web aujourd’hui.

karl Says:

novembre 28th, 2009 at 10:15

REST est un style architectural qui est encore une couche au dessus de HTTP.

Je rejoins Christian dans son analyse. Chacun des domaines est d’ailleurs interprété en fonction de la culture propre des intervenants. Lorsque l’on SPDY de Google qui est une forme d’extension à HTTP. Ils ne s’intéressent proprement dit qu’à l’efficacité du transport et pratiquement pas à l’amélioration du transfert.

Google centralise tous les services dans une même coquille. Sa seule interaction au final n’est avec qu’avec les logiciels clients. L’interopérabilité avec les autres serveurs n’est presque pas un objectif à terme. Ils ont besoin de rapidité, ils ont des besoins spécifiques qu’ils maîtrisent au cœur de leurs applications. Lorsqu’on a créé un écosystème avec un fort contrôle sur tous les éléments du système, on peut se permettre d’imposer sa loi à l’écosystème. Microsoft l’a fait dans l’univers de la bureautique. Google le fait petit à petit pour le Web. Nous n’y sommes pas encore bien sûr.

Pour Google, le transfert n’est pas important ou plutôt il est si peu mis en pratique (quid de HTTP PUT, DELETE, etc., des mime types et des headers) sur le Web aujourd’hui, que Google peut se concentrer sur ce qui améliore le transport des données.

This is a parser for HTTP messages written in C. It parses both requests and responses. The parser is designed to be used in performance HTTP applications. It does not make any allocations, it does not buffer data, and it can be interrupted at anytime. It only requires about 128 bytes of data per message stream (in a web server that is per connection).

chance to investigate the HTTP/1.1 Vary header. As it turns out, there are interesting implications around setting or not setting this header or setting this header incorrectly. Here is my notes on the rationale behind the Vary header, and design guidelines.

To cut a long story short: while reconfiguring my local server to match our production settings I found out that the Vary-header was the actual culprit, and that mod_gzip (a module responsible for compressing content before sending it to the client and thus saving bandwidth) added this particular header, even though we explicitly excluded images from being compressed by this module by means of a mimetype filter (images have a mimetype that matches image/* e.g. image/gif, image/jpeg and so on).

WRT Vary - Based on what Co-advisor sees as well as some of my own testing, Vary is safe in the very limited fashion that if you do a simple, one-dimensional vary, the wrong thing won't be returned.

how you can use Twisted Web's basic or digest HTTP authentication to control access to these resources.

SPDY veut notamment améliorer les délais de latence et diminuer le nombre de connexions nécessaires, avec un nombre «paquets» transmis plus faibles (mais plus denses en information). Les résultats, avec un prototype de serveur et un Chrome optimisé? Un chargement des pages 55% plus rapide.

Today we'd like to share with the web community information about SPDY, pronounced "SPeeDY", an early-stage research project that is part of our effort to make the web faster. SPDY is at its core an application-layer protocol for transporting content over the web. It is designed specifically for minimizing latency through features such as multiplexed streams, request prioritization and HTTP header compression.