Automatic deployment Sat Oct 29 21:01:57 UTC 2016

Author: evert

atom.xml

@@ -3,13 +3,13 @@
     <title><![CDATA[sabre.io]]></title>
     <link href="http://sabre.io/atom.xml" rel="self"/>
     <link href="http://sabre.io/"/>
-    <updated>2016-10-23T19:24:29+00:00</updated>
+    <updated>2016-10-29T21:01:56+00:00</updated>
     <id>http://sabre.io/</id>
         <generator uri="http://sculpin.io/">Sculpin</generator>
             <entry>
             <title type="html"><![CDATA[sabre/event 5 released]]></title>
             <link href="http://sabre.io/blog/2016/sabre-event-5.0.0-release"/>
-            <updated>2016-10-24T02:42:15+00:00</updated>
+            <updated>2016-10-23T19:24:04+00:00</updated>
             <id>http://sabre.io/blog/2016/sabre-event-5.0.0-release</id>
             <content type="html"><![CDATA[<p>We just released sabre/event 5.0.0. This is only a month after the last major
 release, but it's for a good reason.</p>
@@ -29,13 +29,13 @@ anything like this:</p>
 <p>To work with this limitation in coroutines, we treated the last value that
 was passed with <code>yield</code> as the "returned value".</p>
 
-<p>Since PHP 7 it is possible to use return and the PHP Generator object has a
+<p>Since PHP 7 it is possible to use <code>return</code> and the PHP Generator object has a
 <code>getReturn()</code> method to access it.</p>
 
 <p>We missed this in sabre/event 4, but it was quickly pointed out by Felix
 Becker.</p>
 
-<p>Using return makes so much sense now we can, it was worth making a BC break
+<p>Using <code>return</code> makes so much sense now we can, it was worth making a BC break
 for and releasing sabre/event 5 with the more sane behavior for PHP 7.</p>
 
 <p>So today there's a sabre/event 5, and the only change is that if the previous

blog/2016/sabre-event-5.0.0-release/index.html

@@ -42,7 +42,7 @@
         <main>
                 <article>
                 <article class="blog-entry">
-        <time>October 24th, 2016</time>
+        <time>October 23rd, 2016</time>
         <h1>sabre/event 5 released</h1>
         <div>
             <p>We just released sabre/event 5.0.0. This is only a month after the last major
@@ -63,13 +63,13 @@ <h1>sabre/event 5 released</h1>
 <p>To work with this limitation in coroutines, we treated the last value that
 was passed with <code>yield</code> as the "returned value".</p>
 
-<p>Since PHP 7 it is possible to use return and the PHP Generator object has a
+<p>Since PHP 7 it is possible to use <code>return</code> and the PHP Generator object has a
 <code>getReturn()</code> method to access it.</p>
 
 <p>We missed this in sabre/event 4, but it was quickly pointed out by Felix
 Becker.</p>
 
-<p>Using return makes so much sense now we can, it was worth making a BC break
+<p>Using <code>return</code> makes so much sense now we can, it was worth making a BC break
 for and releasing sabre/event 5 with the more sane behavior for PHP 7.</p>
 
 <p>So today there's a sabre/event 5, and the only change is that if the previous

blog/index.html

@@ -45,7 +45,7 @@ <h1>Blog</h1>
                 <p></p>
 
 <article class="blog-entry">
-    <time>October 24th, 2016</time>
+    <time>October 23rd, 2016</time>
     <h1><a href="http://sabre.io/blog/2016/sabre-event-5.0.0-release">sabre/event 5 released</a></h1>
     <p>We just released sabre/event 5.0.0. This is only a month after the last major
 release, but it's for a good reason.</p>
@@ -65,13 +65,13 @@ <h1><a href="http://sabre.io/blog/2016/sabre-event-5.0.0-release">sabre/event 5
 <p>To work with this limitation in coroutines, we treated the last value that
 was passed with <code>yield</code> as the "returned value".</p>
 
-<p>Since PHP 7 it is possible to use return and the PHP Generator object has a
+<p>Since PHP 7 it is possible to use <code>return</code> and the PHP Generator object has a
 <code>getReturn()</code> method to access it.</p>
 
 <p>We missed this in sabre/event 4, but it was quickly pointed out by Felix
 Becker.</p>
 
-<p>Using return makes so much sense now we can, it was worth making a BC break
+<p>Using <code>return</code> makes so much sense now we can, it was worth making a BC break
 for and releasing sabre/event 5 with the more sane behavior for PHP 7.</p>
 
 <p>So today there's a sabre/event 5, and the only change is that if the previous

dav/standards-support/index.html

@@ -152,12 +152,12 @@ <h1>Standards Support</h1>
 </tr>
 <tr>
   <td><a href="http://tools.ietf.org/html/rfc2518">rfc2518</a></td>
-  <td>Obsolete WebDAV specification</td>
+  <td>WebDAV specification (obsolete)</td>
   <td>Implemented.</td>
 </tr>
 <tr>
   <td><a href="http://tools.ietf.org/html/rfc2617">rfc2617</a></td>
-  <td>HTTP Basic/Digest auth</td>
+  <td>HTTP Basic/Digest auth (obsolete)</td>
   <td><a href="/dav/authentication/">Authentication plugin</a>.</td>
 </tr>
 <tr>
@@ -335,6 +335,11 @@ <h1>Standards Support</h1>
   <td>Prefer Header for HTTP</td>
   <td>Parsed by <a href="/http/">sabre/http</a>, supported in core.</td>
 </tr>
+<tr>
+  <td><a href="https://tools.ietf.org/html/rfc7617" title="The 'Basic' HTTP Authentication Scheme">rfc7617</a></td>
+  <td>'Basic' HTTP Authentication</td>
+  <td><a href="/dav/authentication/">Authentication plugin</a>.</td>
+</tr>
 </tbody>
 </table>
 

event/coroutines/index.html

@@ -138,8 +138,7 @@ <h2 id="after">After</h2>
 <h2 id="tips-and-tricks">Tips and tricks</h2>
 
 <p>The coroutines itself also returns a promise. This promise will resolve with
-the last yielded value or promise. It will reject if there was an uncaught
-exception.</p>
+the value you returned from the coroutine.</p>
 
 <p>This allows you to for example call <code>wait()</code> to turn a large asynchronous
 process into a blocking one:</p>
@@ -158,17 +157,6 @@ <h2 id="tips-and-tricks">Tips and tricks</h2>
 
 <pre><code>use Sabre\Event;
 
-Event\coroutine(function() {
-
-    yield Event\coroutine($anotherGenerator);
-
-});
-</code></pre>
-
-<p>In PHP7 this becomes even easier:</p>
-
-<pre><code>use Sabre\Event;
-
 Event\coroutine(function() {
 
     yield from $anotherGenerator;

event/install/index.html

@@ -89,7 +89,7 @@ <h2 id="installing-with-composer">Installing with composer</h2>
 
 <p>From your project directory, the easiest is then to simply call:</p>
 
-<pre><code>composer require sabre/event ~4
+<pre><code>composer require sabre/event ~5
 </code></pre>
 
 <p>This rule ensures that you install the latest event package in the 1.0 range

index.html

@@ -139,7 +139,7 @@ <h3>We provide:</h3>
         <section class="box box--news">
             <h1>News</h1>
                             <article class="blog-entry">
-                    <time>Oct. 24th, 2016</time>
+                    <time>Oct. 23rd, 2016</time>
                     <h1><a href="http://sabre.io/blog/2016/sabre-event-5.0.0-release">sabre/event 5 released</a></h1>
                     <p>We just released sabre/event 5.0.0. This is only a month after the last major
 release, but it's for a good reason.</article>