<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<small>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style></style> </small>
<table class="backgroundTable" cellpadding="0" cellspacing="0"
bgcolor="#ffffff" width="100%">
<tbody>
<tr>
<td align="left" valign="top">
<table cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="border-top: 0px solid rgb(0, 0, 0);
border-bottom: 1px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255); text-align:
center;" align="center"><span style="font-size:
10px; color: rgb(96, 96, 96); line-height: 200%;
font-family: verdana; text-decoration: none;">Email
not
displaying correctly? <a
href="http://www.oplin.org/4cast/"
style="font-size: 10px; color: rgb(0, 0, 255);
line-height: 200%; font-family: verdana;
text-decoration: none;">View
it in your browser.</a></span></td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(51, 51, 51);
border-bottom: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255);">
<center><a href=""><img id="editableImg1"
src="cid:part2.03050505.04070506@oplin.org"
title="OPLIN" alt="OPLIN 4Cast" border="0"
align="middle"></a></center>
</td>
</tr>
</tbody>
</table>
<table style="width: 763px; height: 877px;" cellpadding="20"
cellspacing="0" bgcolor="#ffffff">
<tbody>
<tr>
<td style="font-size: 12px; color: rgb(0, 0, 0);
line-height: 150%; font-family: trebuchet ms;"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
bgcolor="#ffffff" valign="top">
<p><!-- Make sure you modify the 4Cast title in this section -->
<span style="font-size: 20px; font-weight: bold;
color: rgb(0, 0, 0); font-family: arial;
line-height: 110%;">OPLIN 4cast #426: The next
version of HTTP</span><br>
<!-- Make sure you modify the date of the 4Cast in this section -->
<span style="font-size: 11px; font-weight: normal;
color: rgb(102, 102, 102); font-style: italic;
font-family: arial;">February 25th, 2015</span></p>
<!-- Begin copy of Web Source here -->
<p style="text-align: justify;font-size: 16px;
font-family: arial; line-height: 110%;"><img
src="cid:part4.04000009.00080203@oplin.org"
alt="Hypertext Transfer Protocol" align="left"
height="65" width="110">Last week, the Internet
Engineering Steering Group (IESG) posted a <a
href="https://lists.w3.org/Archives/Public/ietf-http-wg/2015JanMar/0478.html">message</a>
stating that they had "...approved the following
document: 'Hypertext Transfer Protocol version
2'...as Proposed Standard." While this sounds
pretty innocuous and/or cryptic to many of us,
this announcement actually marked the official
beginning of HTTP/2, the long-awaited successor to
HTTP/1.1, the information transfer protocol
currently used by the World Wide Web (allowing the
hypertext linking between web pages mentioned in
last week's <em>4cast</em>). While that still may
not mean much to most of us, we should all notice
that the Web will respond a bit faster in the
future than it does now, once HTTP/2 becomes the
common standard.
</p>
<div> </div>
<ul style="text-align: left;">
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://www.businessinsider.com/the-internet-is-about-to-get-faster--heres-why-2015-2">The
internet is about to get faster - here's why</a>
(Business Insider | Peter Maynard) "When a web
page is requested, the server sends back the
page, but must wait for the web browser to parse
the page's HTML and issue further requests for
things it finds in the code, such as images.
Server push allows the server to send all the
resources associated with a page when the page
is requested, without waiting. This will cut a
lot of the latency associated with web
connections. Once web servers and web browsers
start implementing HTTP/2 - which could be as
soon as a few weeks from now - the web-browsing
experience will feel quicker and more
responsive."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://readwrite.com/2015/02/18/http-update-http2-what-you-need-to-know">Everything
you need to know about HTTP2</a> (ReadWrite |
Lauren Orsini) "For the past 16 years, HTTP has
basically done the heavy lifting of bringing Web
pages to your browser. When you type a URL into
your browser bar-readwrite.com, for
instance-you're actually creating an HTTP
request to the Web server that instructs it to
find and deliver a particular Web page. But HTTP
has its limits. Modern Web pages pack in more
features than just about anyone imagined back in
1999, making it <a
href="http://httparchive.org/trends.php#bytesTotal&reqTotal">more
resource-intensive than ever</a> just to load
them in a browser."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://arstechnica.com/information-technology/2015/02/http2-finished-coming-to-browsers-within-weeks/">HTTP/2
finished, coming to browsers within weeks</a>
(Ars Technica | Peter Bright) "In HTTP/2,
multiple bidirectional streams are multiplexed
over a single TCP connection. Each stream can
carry a request/response pair, and multiple
requests to a server can be made by using
multiple streams. However, the streams are all
independent; if one stream is slow, the HTTP/2
connection can still be used to transfer data
belonging to other streams. Similarly, a client
can request a large object and then a small
object, and the response to the small object can
be given before, or even during, the response to
the large object."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://venturebeat.com/2015/02/18/dont-blame-yourself-for-ignoring-http2-the-biggest-http-update-in-years/">Don't
blame yourself for ignoring HTTP/2, the
biggest HTTP update in years</a> (VentureBeat
| Cullen Macdonald) "HTTP/2 is for sure going to
add to the increase in rate of change for things
on the Internet, but it'll do it without being
noticed. It will continue to be incorporated
into more websites you visit, and browsers will
more fully support the official spec. There
won't ever be an explosion of speed from your
phone's browser where you'll ask yourself 'oh!
is today HTTP/2 day?!'"</li>
</ul>
<div style="text-align: left;"> </div>
<p style="text-align: left; font-size: 20px;
font-family: arial; line-height: 110%;"><small><strong><em>Articles
from <a href="http://ohioweblibrary.org">Ohio
Web Library</a>:</em></strong></small><br>
</p>
<div style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;">
<ul>
<li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=cdb942e7-83ac-40eb-98bf-3d98c2d65901%40sessionmgr4003&vid=0&hid=4114&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=92603687">Making
the web faster with HTTP 2.0.</a> (<em>Communications
of the ACM</em>, Dec. 2013, p42-49 | Ilya
Grigorik)</li>
<li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=61363b41-b226-4f98-b4bb-f242d3cf975b%40sessionmgr113&vid=0&hid=101&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=84348443">SPDYing
up the Web.</a> (<em>Communications of the
ACM</em>, Dec. 2012, p64-73 | Bryce Thomas,
Raja Jurdak, and Ian Atkinson)</li>
<li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/ehost/detail/detail?sid=bd058d2f-4e29-4843-864f-22639bcebbda%40sessionmgr111&vid=0&hid=101&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=sch&AN=61356668">The
slow-motion Internet.</a> (<em>Technology
Review</em>, March/April 2011, p54-58 |
Erica Naone)</li>
</ul>
</div>
<div style="text-align: left;"> </div>
<!-- End paste of web source here --> </td>
</tr>
<tr>
<td style="" solid="" background-color:="" rgb(255,=""
255,="" 255);="" >=""
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
valign="top" width="760"><span style="font-size:
10px; color: rgb(96, 96, 96); line-height: 100%;
font-family: verdana;">
<hr><!-- Begin standard subscription verbiage -->
<div style="text-align: justify;">The <strong><em>OPLIN
4cast</em></strong>
is a weekly compilation of
recent headlines, topics, and trends that could
impact public
libraries. You can subscribe to it in a variety
of ways, such as: <br>
</div>
<div style="text-align: left;"> </div>
<ul>
<li style="text-align: justify;"><strong>RSS
feed.</strong>
You
can receive the OPLIN 4cast
via RSS feed by subscribing to the following
URL:
<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/index.php/?feed=rss2">http://www.oplin.org/4cast/index.php/?feed=rss2</a>.
</li>
<li style="text-align: justify;"><strong>Live
Bookmark.</strong>
If you're using the Firefox
web browser, you can go to the 4cast website
(<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/">http://www.oplin.org/4cast/</a>) and click on the
orange "radio wave" icon
on the right side of the address bar. In
Internet Explorer 7, click on
the same icon to view or subscribe to the
4cast RSS feed. </li>
<li style="text-align: justify;"><strong>E-mail.</strong>
You
can have the OPLIN 4cast
delivered via e-mail (a'la OPLINlist and
OPLINtech) by subscribing to
the 4cast mailing list at
<a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/OPLIN4cast">http://mail.oplin.org/mailman/listinfo/OPLIN4cast</a>.
</li>
</ul>
</span> </td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 204);"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg"
valign="top" width="760"> <br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<small>
<title>OPLIN 4Cast</title>
<style>
.headerTop { background-color:#FFFFFF; border-top:0px solid #000000; border-bottom:1px solid #FFFFFF; text-align:center; }
.adminText { font-size:16px; color:#0000FF; line-height:200%; font-family:verdana; text-decoration:none; }
.headerBar { background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:0px solid #FFFFFF; }
.title { font-size:20px; font-weight:bold; color:#000000; font-family:arial; line-height:110%; }
.subTitle { font-size:11px; font-weight:normal; color:#000000; font-style:italic; font-family:arial; }
.defaultText { font-size:12px; color:#000000; line-height:150%; font-family:trebuchet ms; }
.footerRow { background-color:#FFFFCC; border-top:0px solid #FFFFFF; }
.footerText { font-size:10px; color:#996600; line-height:100%; font-family:verdana; }
a { color:#0000FF; color:#0000FF; color:#0000FF; }
</style>
</small>
</body>
</html>