About: Hypertext Transfer Protocol is a research topic. Over the lifetime, 2698 publications have been published within this topic receiving 46847 citations. The topic is also known as: HTTP & http://.
TL;DR: The Hypertext Transfer Protocol is an application-level protocol for distributed, collaborative, hypermedia information systems, which can be used for many tasks beyond its use for hypertext through extension of its request methods, error codes and headers.
Abstract: The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers [47]. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred.
TL;DR: A new hypertext resource discovery system called a Focused Crawler that is robust against large perturbations in the starting set of URLs, and capable of exploring out and discovering valuable resources that are dozens of links away from the start set, while carefully pruning the millions of pages that may lie within this same radius.
TL;DR: This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol, referred to as HTTP version 2 (HTTP/2), which enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection.
Abstract: This specification describes an optimized expression of the semantics
of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version
2 (HTTP/2). HTTP/2 enables a more efficient use of network resources
and a reduced perception of latency by introducing header field
compression and allowing multiple concurrent exchanges on the same
connection. It also introduces unsolicited push of representations
from servers to clients. This specification is an alternative to, but
does not obsolete, the HTTP/1.1 message syntax. HTTP's existing
semantics remain unchanged.
TL;DR: This paper presents their DASH dataset including the DASHEncoder, an open source DASH content generation tool, and provides basic evaluations of the different segment lengths, the influence of HTTP server settings, and shows some of the advantages as well as problems of shorter segment lengths.
Abstract: The delivery of audio-visual content over the Hypertext Transfer Protocol (HTTP) got lot of attention in recent years and with dynamic adaptive streaming over HTTP (DASH) a standard is now available. Many papers cover this topic and present their research results, but unfortunately all of them use their own private dataset which -- in most cases -- is not publicly available. Hence, it is difficult to compare, e.g., adaptation algorithms in an objective way due to the lack of a common dataset which shall be used as basis for such experiments. In this paper, we present our DASH dataset including our DASHEncoder, an open source DASH content generation tool. We also provide basic evaluations of the different segment lengths, the influence of HTTP server settings, and, in this context, we show some of the advantages as well as problems of shorter segment lengths.