当前位置: 首页 > news >正文

【HTTP】Speed and Mobility: An Approach for HTTP 2.0 to Make Mobile Apps and the Web Faster

This week begins face to face meetings at the IETF on how to approach HTTP 2.0 and improve the Internet. How the industry moves forward together on the next version of HTTP – how every application and service on the web communicates today – can positively impact user experience, operational and environmental costs, and even the battery life of the devices you carry around.

As part of this discussion of HTTP 2.0, Microsoft will submit to the IETF a proposal for “HTTP Speed+Mobility." The approach we propose focuses on all the web’s end users – emphasizing performance improvements and security while at the same time accounting for the important needs of mobile devices and applications.

Why HTTP 2.0?

Today’s HTTP has historical limitations based on what used to be good enough for the web. Because of this, the HTTPbis working group in the Internet Engineering Task Force (IETF) has approved a new charter to define HTTP “2.0” to address performance limitations with HTTP. The working group’s explicit goal is to keep compatibility with existing applications and scenarios, specifically to preserve the existing semantics of HTTP.

Why this approach?

Improving HTTP starts with speed. There is already broad consensus about the need to make web browsing much faster.

We think that apps—not just browsers—should get faster too. More and more, apps are how people access web services, in addition to their browser.

Improving HTTP should also make mobile better. For example, people want their mobile devices to have better battery life. HTTP 2.0 can help decrease the power consumption of network access. Mobile devices also give people a choice of networks with different costs and bandwidth limits. Embedded sensors and clients face similar issues. HTTP 2.0 can make this better.

This approach includes keeping people and their apps in control of network access. Specifically, the client remains in control over the content that it receives from the web. This extends a key attribute of the existing HTTP protocol that has served the Web well. The app or browser is in the best position to assess what the user is currently doing and what data is already locally available. This approach enables apps and browsers to innovate more freely, delivering the most relevant content to the user based on the user’s actual needs.

We think that rapid adoption of HTTP 2.0 is important. To make that happen, HTTP 2.0 needs to retain as much compatibility as possible with the existing Web infrastructure. Awareness of HTTP is built into nearly every switch, router, proxy, load balancer, and security system in use today. If the new protocol is “HTTP” in name only, upgrading all of this infrastructure would take too long. By building on existing web standards, the community can set HTTP 2.0 up for rapid adoption throughout the web.

Done right, HTTP 2.0 can help people connect their devices and applications to the Internet fast, reliably, and securely over a number of diverse networks, with great battery life and low cost.

How?

The HTTP Speed+Mobility proposal starts from both the Google SPDY protocol (a separate submission to the IETF for this discussion) and the work the industry has done around WebSockets.

SPDY has done a great job raising awareness of web performance and taking a “clean slate” approach to improving HTTP to make the Web faster. The main departures from SPDY are to address the needs of mobile devices and applications.

Looking ahead

We are looking forward to a vigorous, open discussion within the IETF around the design of HTTP 2.0. We are excited by the promise of an HTTP 2.0 that will serve the Internet for decades to come. As the effort progresses, we will continue to provide updates on this blog. Consistent with our other web standards engagements, we will also provide early implementations of the HTTP 2.0 specification on the HTML5 Labs site.

- Sandeep Singhal, Group Program Manager, Windows Core Networking

 

http://blogs.msdn.com/b/interoperability/archive/2012/03/26/speed-and-mobility-an-approach-for-http-2-0-to-make-mobile-apps-and-the-web-faster.aspx

相关文章:

  • 蛰伏多年的 HTML5 创业者,终于被送上了风口
  • android开发(34) 自定义 listView的分割线( 使用xml drawable画多条线)
  • elasticsearch常用操作命令
  • 【实习记】2014-09-04浏览代码查middle资料+总结我折腾过的源码浏览器
  • 查找字符串中出现最多的字符
  • xshell 4 中文乱码问题解决
  • Html的空格显示
  • Java基础-Date类常用方法介绍
  • 910
  • 区块链研习 | DAG网络:Blockless无区块概念将解决区块链交易性能问题
  • jQuery 自制上传头像插件-附带Demo实例(ajaxfileupload.js第三弹)
  • 干货 | 手把手教你用python实现新浪微博模拟登陆,超详细
  • 百度编辑器ueditor 在vs2008中的使用方法
  • cordova 建立工程生成apk
  • 回流、重绘及其优化
  • IE9 : DOM Exception: INVALID_CHARACTER_ERR (5)
  • 分享一款快速APP功能测试工具
  • __proto__ 和 prototype的关系
  • CSS魔法堂:Absolute Positioning就这个样
  • IIS 10 PHP CGI 设置 PHP_INI_SCAN_DIR
  • Java 最常见的 200+ 面试题:面试必备
  • React as a UI Runtime(五、列表)
  • Selenium实战教程系列(二)---元素定位
  • VuePress 静态网站生成
  • 计算机在识别图像时“看到”了什么?
  • 前端相关框架总和
  • 微信端页面使用-webkit-box和绝对定位时,元素上移的问题
  • d²y/dx²; 偏导数问题 请问f1 f2是什么意思
  • 教程:使用iPhone相机和openCV来完成3D重建(第一部分) ...
  • ​​​​​​​​​​​​​​Γ函数
  • ​LeetCode解法汇总307. 区域和检索 - 数组可修改
  • ​TypeScript都不会用,也敢说会前端?
  • ​低代码平台的核心价值与优势
  • #NOIP 2014#day.2 T1 无限网络发射器选址
  • #我与Java虚拟机的故事#连载04:一本让自己没面子的书
  • (1) caustics\
  • (2)nginx 安装、启停
  • (C语言)fread与fwrite详解
  • (C语言)逆序输出字符串
  • (pojstep1.1.2)2654(直叙式模拟)
  • (Redis使用系列) SpringBoot 中对应2.0.x版本的Redis配置 一
  • (介绍与使用)物联网NodeMCUESP8266(ESP-12F)连接新版onenet mqtt协议实现上传数据(温湿度)和下发指令(控制LED灯)
  • (六)激光线扫描-三维重建
  • (三)Pytorch快速搭建卷积神经网络模型实现手写数字识别(代码+详细注解)
  • (深入.Net平台的软件系统分层开发).第一章.上机练习.20170424
  • (四)Android布局类型(线性布局LinearLayout)
  • (五)网络优化与超参数选择--九五小庞
  • (转)http-server应用
  • (转)机器学习的数学基础(1)--Dirichlet分布
  • ./configure,make,make install的作用
  • .equal()和==的区别 怎样判断字符串为空问题: Illegal invoke-super to void nio.file.AccessDeniedException
  • .NET Framework 服务实现监控可观测性最佳实践
  • .NET教程 - 字符串 编码 正则表达式(String Encoding Regular Express)
  • .net最好用的JSON类Newtonsoft.Json获取多级数据SelectToken
  • @JSONField或@JsonProperty注解使用