 - HTTP 1.1 is the latest version of Hypertext Transfer Protocol (HTTP), the World Wide Web application protocol that runs on top of the Internet's TCP/IP suite of protocols. HTTP 1.1 provides faster delivery of Web pages than the original HTTP and reduces Web traffic. Developed by a committee of the Internet Engineering Task Force (IETF) that includes the Web's chief creator Tim Berners-Lee, HTTP 1.1 is supported by the latest Web servers and browsers.Here's a summary of how HTTP 1.1 makes information flow faster: - Instead of opening and closing a connection for each application request, HTTP 1.1 provides a persistent connection that allows multiple requests to be batched or pipelined to an output buffer . The underlying Transmission Control Protocol layer can put multiple requests (and responses to requests) into one TCP segment that gets forwarded to the Internet Protocol layer for packet transmission. Because the number of connection and disconnection requests for a sequence of "get a file" requests is reduced, fewer packets need to flow across the Internet. Since requests are pipelined, TCP segments are more efficient. The overall result is less Internet traffic and faster performance for the user. Persistent connection is similar to Netscape's HTTP 1.0 extension called KeepAlive, but provides better handling of requests that go through proxy servers.
- When a browser supporting HTTP 1.1 indicates it can decompress HTML files, a server will compress them for transport across the Internet, providing a substantial aggregate savings in the amount of data that has to be transmitted. (Image files are already in a compressed format so this improvement applies only to HTML and other non-image data types.)
In addition to persistent connections and other performance improvements, HTTP 1.1 also provides the ability to have multiple domain names share the same Internet address (IP address). This simplifies processing for Web servers that host a number of Web sites in what is sometimes called virtual hosting.
 |
Learn more about SOA and Web services standards |
| Cisco's next-generation AON architecture: What will it mean for Web services?: In this second of a two-part column, Preston Gralla examines how Cisco's AON will impact applications, Web services standards and network architecture. |
| Standard Web services stack remains illusive SOA goal: A single Web services stack all vendors can agree on may be a laudable goal, but even Apache Axis 2.0 does not believe it is reachable and argues that competition might be good. |
| When all else fails, try SOA best practices: For confused about SOA standards, tools and technologies, and not sure where to begin an implementation, you are not alone, say three analysts who specialize in SOA best practices. |
| Seven smart statements about SOA: SOA management, the SOA business case and the limits of Web services standards are among the topics covered of late by some of the brighter minds in the SOA arena. |
| Web services standards: It's getting harder to keep up with all the Web services standards out there. Which new ones or standards on the near horizon do you think we should be watching and why? |
| Podcast: SOA and multi-core processing: In this podcast, Rogue Wave Software CEO Cory Isaacson will discuss how to get Web services to scale on multi-core processors, how multi-core affects order of processing concerns and what defines ... |
| Special report: Java EE 5 faces the SOA test: This series looks at what service-oriented principles Java EE 5 has embraced, if the platform offers enough simplicity and what role industry experts expect it to play. |
| The top SOA/Web services stories of 2006: This two part year-in-review articles includes WS-Policy, agile development, the changing ESB and Eclipse getting more involved with SOA and Web services |
| Eclipse Tutorial: Want to learn more about Eclipse? Check out the language-neutral Eclipse development platform featuring an extensible plug-in based framework. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| LAST UPDATED: |
02 Aug 2003
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
