From c807880f7ac73f813b2660ea81a00f7712a4e793 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 29 Aug 2016 12:39:49 +0200 Subject: Add old mailing list archives --- .../20150624/204c1308/attachment-0001.html | 4 ++ .../attachments/20150624/204c1308/attachment.html | 4 ++ .../20150624/6d15706e/attachment-0001.html | 9 +++ .../attachments/20150624/6d15706e/attachment.html | 9 +++ .../20150624/72689ab9/attachment-0001.html | 72 ++++++++++++++++++++ .../attachments/20150624/72689ab9/attachment.html | 72 ++++++++++++++++++++ .../20150624/b67122b6/attachment-0001.html | 77 ++++++++++++++++++++++ .../attachments/20150624/b67122b6/attachment.html | 77 ++++++++++++++++++++++ 8 files changed, 324 insertions(+) create mode 100644 _build/static/archives/extend/attachments/20150624/204c1308/attachment-0001.html create mode 100644 _build/static/archives/extend/attachments/20150624/204c1308/attachment.html create mode 100644 _build/static/archives/extend/attachments/20150624/6d15706e/attachment-0001.html create mode 100644 _build/static/archives/extend/attachments/20150624/6d15706e/attachment.html create mode 100644 _build/static/archives/extend/attachments/20150624/72689ab9/attachment-0001.html create mode 100644 _build/static/archives/extend/attachments/20150624/72689ab9/attachment.html create mode 100644 _build/static/archives/extend/attachments/20150624/b67122b6/attachment-0001.html create mode 100644 _build/static/archives/extend/attachments/20150624/b67122b6/attachment.html (limited to '_build/static/archives/extend/attachments/20150624') diff --git a/_build/static/archives/extend/attachments/20150624/204c1308/attachment-0001.html b/_build/static/archives/extend/attachments/20150624/204c1308/attachment-0001.html new file mode 100644 index 00000000..961f2d3b --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/204c1308/attachment-0001.html @@ -0,0 +1,4 @@ + +<div dir="ltr"><div><div><div><div>hello,<br><br></div>According to you grate support I got from you at yesterday, I could continue my project, where I use Cowboy webserver and using Websocket. Now I made an own web page with basic features I need, so the server and client can communicates to eachother. I like it. <br><br>Now I would like to step forward, and I would like to implement a Request-Response mechanism. I read few articles in to this topic, and all of them has mentioned this "feature" is not part of the Websocket standard. They were suggested to use some sub-protocols for this, but I did not see any written in Erlang.<br><br></div>So, I would like to ask you, do I understand right that Cowboy does not have this feature too? If so, do you have some idea how can I implement a basic request-response mechanism? Probably one of you guys in this forum have some idea.<br><br></div><div>Btw, the links I read about this topic:<br>    <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>    <a href="http://alabor.me/articles/request-response-oriented-websockets/">http://alabor.me/articles/request-response-oriented-websockets/</a><br>    <a href="https://www.npmjs.com/package/primus-responder">https://www.npmjs.com/package/primus-responder</a><br></div><div><br></div>thanks for your help,<br></div>/Robi<br></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/204c1308/attachment.html b/_build/static/archives/extend/attachments/20150624/204c1308/attachment.html new file mode 100644 index 00000000..961f2d3b --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/204c1308/attachment.html @@ -0,0 +1,4 @@ + +<div dir="ltr"><div><div><div><div>hello,<br><br></div>According to you grate support I got from you at yesterday, I could continue my project, where I use Cowboy webserver and using Websocket. Now I made an own web page with basic features I need, so the server and client can communicates to eachother. I like it. <br><br>Now I would like to step forward, and I would like to implement a Request-Response mechanism. I read few articles in to this topic, and all of them has mentioned this "feature" is not part of the Websocket standard. They were suggested to use some sub-protocols for this, but I did not see any written in Erlang.<br><br></div>So, I would like to ask you, do I understand right that Cowboy does not have this feature too? If so, do you have some idea how can I implement a basic request-response mechanism? Probably one of you guys in this forum have some idea.<br><br></div><div>Btw, the links I read about this topic:<br>    <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>    <a href="http://alabor.me/articles/request-response-oriented-websockets/">http://alabor.me/articles/request-response-oriented-websockets/</a><br>    <a href="https://www.npmjs.com/package/primus-responder">https://www.npmjs.com/package/primus-responder</a><br></div><div><br></div>thanks for your help,<br></div>/Robi<br></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/6d15706e/attachment-0001.html b/_build/static/archives/extend/attachments/20150624/6d15706e/attachment-0001.html new file mode 100644 index 00000000..3d01eba7 --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/6d15706e/attachment-0001.html @@ -0,0 +1,9 @@ + +<div dir="ltr">I think you'd have to roll your own, you just need some way to <a href="http://www.enterpriseintegrationpatterns.com/CorrelationIdentifier.html" target="_blank">correlate</a> responses with the originating request. OTP does something similar under the hood with gen_server <a href="http://www.erlang.org/doc/man/gen_server.html#call-2" target="_blank">calls</a>.<div><br></div><div>It's also possible to treat the ws connection as a messaging channel, and use something like <a href="http://www.enterpriseintegrationpatterns.com/MessageSelector.html" target="_blank">selective consumer</a> to de-multiplex the messages. e.g. you could add a type/channel field to each message, and only subscribe to those messages.</div><div><br></div><div>Remember that once you move into an async world, there are no guarantees that you will receive a response! So you need to start thinking about timeouts etc.</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 June 2015 at 10:18, Robert Balogh <span dir="ltr"><<a href="mailto:ethrbh@gmail.com" target="_blank">ethrbh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>hello,<br><br></div>According to you grate support I got from you at yesterday, I could continue my project, where I use Cowboy webserver and using Websocket. Now I made an own web page with basic features I need, so the server and client can communicates to eachother. I like it. <br><br>Now I would like to step forward, and I would like to implement a Request-Response mechanism. I read few articles in to this topic, and all of them has mentioned this "feature" is not part of the Websocket standard. They were suggested to use some sub-protocols for this, but I did not see any written in Erlang.<br><br></div>So, I would like to ask you, do I understand right that Cowboy does not have this feature too? If so, do you have some idea how can I implement a basic request-response mechanism? Probably one of you guys in this forum have some idea.<br><br></div><div>Btw, the links I read about this topic:<br>    <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol" target="_blank">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>    <a href="http://alabor.me/articles/request-response-oriented-websockets/" target="_blank">http://alabor.me/articles/request-response-oriented-websockets/</a><br>    <a href="https://www.npmjs.com/package/primus-responder" target="_blank">https://www.npmjs.com/package/primus-responder</a><br></div><div><br></div>thanks for your help,<br></div>/Robi<br></div>
+<br>_______________________________________________<br>
+Extend mailing list<br>
+<a href="mailto:Extend@lists.ninenines.eu">Extend@lists.ninenines.eu</a><br>
+<a href="https://lists.ninenines.eu/listinfo/extend" rel="noreferrer" target="_blank">https://lists.ninenines.eu/listinfo/extend</a><br>
+<br></blockquote></div><br></div></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/6d15706e/attachment.html b/_build/static/archives/extend/attachments/20150624/6d15706e/attachment.html new file mode 100644 index 00000000..3d01eba7 --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/6d15706e/attachment.html @@ -0,0 +1,9 @@ + +<div dir="ltr">I think you'd have to roll your own, you just need some way to <a href="http://www.enterpriseintegrationpatterns.com/CorrelationIdentifier.html" target="_blank">correlate</a> responses with the originating request. OTP does something similar under the hood with gen_server <a href="http://www.erlang.org/doc/man/gen_server.html#call-2" target="_blank">calls</a>.<div><br></div><div>It's also possible to treat the ws connection as a messaging channel, and use something like <a href="http://www.enterpriseintegrationpatterns.com/MessageSelector.html" target="_blank">selective consumer</a> to de-multiplex the messages. e.g. you could add a type/channel field to each message, and only subscribe to those messages.</div><div><br></div><div>Remember that once you move into an async world, there are no guarantees that you will receive a response! So you need to start thinking about timeouts etc.</div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 June 2015 at 10:18, Robert Balogh <span dir="ltr"><<a href="mailto:ethrbh@gmail.com" target="_blank">ethrbh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>hello,<br><br></div>According to you grate support I got from you at yesterday, I could continue my project, where I use Cowboy webserver and using Websocket. Now I made an own web page with basic features I need, so the server and client can communicates to eachother. I like it. <br><br>Now I would like to step forward, and I would like to implement a Request-Response mechanism. I read few articles in to this topic, and all of them has mentioned this "feature" is not part of the Websocket standard. They were suggested to use some sub-protocols for this, but I did not see any written in Erlang.<br><br></div>So, I would like to ask you, do I understand right that Cowboy does not have this feature too? If so, do you have some idea how can I implement a basic request-response mechanism? Probably one of you guys in this forum have some idea.<br><br></div><div>Btw, the links I read about this topic:<br>    <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol" target="_blank">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>    <a href="http://alabor.me/articles/request-response-oriented-websockets/" target="_blank">http://alabor.me/articles/request-response-oriented-websockets/</a><br>    <a href="https://www.npmjs.com/package/primus-responder" target="_blank">https://www.npmjs.com/package/primus-responder</a><br></div><div><br></div>thanks for your help,<br></div>/Robi<br></div>
+<br>_______________________________________________<br>
+Extend mailing list<br>
+<a href="mailto:Extend@lists.ninenines.eu">Extend@lists.ninenines.eu</a><br>
+<a href="https://lists.ninenines.eu/listinfo/extend" rel="noreferrer" target="_blank">https://lists.ninenines.eu/listinfo/extend</a><br>
+<br></blockquote></div><br></div></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/72689ab9/attachment-0001.html b/_build/static/archives/extend/attachments/20150624/72689ab9/attachment-0001.html new file mode 100644 index 00000000..fb95808d --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/72689ab9/attachment-0001.html @@ -0,0 +1,72 @@ + +<div dir="ltr"><div><div><div><div>hello,<br><br></div>I would like to thanks the response to all of you. I will try keep all these in my mind.<br><br></div>@Bas, thanks for your note about <a href="https://github.com/bwegh/erwa" target="_blank">erwa</a>, I will take a look.<br><br></div>thanks again,<br></div>/Robi<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-24 12:28 GMT+02:00 Bas Wegh <span dir="ltr"><<a href="mailto:BasWegh@gmx.de" target="_blank">BasWegh@gmx.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+  
+    
+  
+  <div bgcolor="#FFFFFF" text="#000000">
+    hello Robi,<br>
+    <br>
+    you might be interested in erwa:<br>
+    <a href="https://github.com/bwegh/erwa" target="_blank">https://github.com/bwegh/erwa</a><br>
+    <br>
+    Cheers,<br>
+    Bas<span class=""><br>
+    <br>
+    <div>On 06/24/2015 11:18 AM, Robert Balogh
+      wrote:<br>
+    </div>
+    </span><blockquote type="cite"><div><div class="h5">
+      <div dir="ltr">
+        <div>
+          <div>
+            <div>
+              <div>hello,<br>
+                <br>
+              </div>
+              According to you grate support I got from you at
+              yesterday, I could continue my project, where I use Cowboy
+              webserver and using Websocket. Now I made an own web page
+              with basic features I need, so the server and client can
+              communicates to eachother. I like it. <br>
+              <br>
+              Now I would like to step forward, and I would like to
+              implement a Request-Response mechanism. I read few
+              articles in to this topic, and all of them has mentioned
+              this "feature" is not part of the Websocket standard. They
+              were suggested to use some sub-protocols for this, but I
+              did not see any written in Erlang.<br>
+              <br>
+            </div>
+            So, I would like to ask you, do I understand right that
+            Cowboy does not have this feature too? If so, do you have
+            some idea how can I implement a basic request-response
+            mechanism? Probably one of you guys in this forum have some
+            idea.<br>
+            <br>
+          </div>
+          <div>Btw, the links I read about this topic:<br>
+            Â Â Â  <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol" target="_blank">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>
+            Â Â Â  <a href="http://alabor.me/articles/request-response-oriented-websockets/" target="_blank">http://alabor.me/articles/request-response-oriented-websockets/</a><br>
+            Â Â Â  <a href="https://www.npmjs.com/package/primus-responder" target="_blank">https://www.npmjs.com/package/primus-responder</a><br>
+          </div>
+          <div><br>
+          </div>
+          thanks for your help,<br>
+        </div>
+        /Robi<br>
+      </div>
+      <br>
+      <fieldset></fieldset>
+      <br>
+      </div></div><span class=""><pre>_______________________________________________
+Extend mailing list
+<a href="mailto:Extend@lists.ninenines.eu" target="_blank">Extend@lists.ninenines.eu</a>
+<a href="https://lists.ninenines.eu/listinfo/extend" target="_blank">https://lists.ninenines.eu/listinfo/extend</a>
+</pre>
+    </span></blockquote>
+    <br>
+  </div>
+
+</blockquote></div><br></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/72689ab9/attachment.html b/_build/static/archives/extend/attachments/20150624/72689ab9/attachment.html new file mode 100644 index 00000000..fb95808d --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/72689ab9/attachment.html @@ -0,0 +1,72 @@ + +<div dir="ltr"><div><div><div><div>hello,<br><br></div>I would like to thanks the response to all of you. I will try keep all these in my mind.<br><br></div>@Bas, thanks for your note about <a href="https://github.com/bwegh/erwa" target="_blank">erwa</a>, I will take a look.<br><br></div>thanks again,<br></div>/Robi<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-06-24 12:28 GMT+02:00 Bas Wegh <span dir="ltr"><<a href="mailto:BasWegh@gmx.de" target="_blank">BasWegh@gmx.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+  
+    
+  
+  <div bgcolor="#FFFFFF" text="#000000">
+    hello Robi,<br>
+    <br>
+    you might be interested in erwa:<br>
+    <a href="https://github.com/bwegh/erwa" target="_blank">https://github.com/bwegh/erwa</a><br>
+    <br>
+    Cheers,<br>
+    Bas<span class=""><br>
+    <br>
+    <div>On 06/24/2015 11:18 AM, Robert Balogh
+      wrote:<br>
+    </div>
+    </span><blockquote type="cite"><div><div class="h5">
+      <div dir="ltr">
+        <div>
+          <div>
+            <div>
+              <div>hello,<br>
+                <br>
+              </div>
+              According to you grate support I got from you at
+              yesterday, I could continue my project, where I use Cowboy
+              webserver and using Websocket. Now I made an own web page
+              with basic features I need, so the server and client can
+              communicates to eachother. I like it. <br>
+              <br>
+              Now I would like to step forward, and I would like to
+              implement a Request-Response mechanism. I read few
+              articles in to this topic, and all of them has mentioned
+              this "feature" is not part of the Websocket standard. They
+              were suggested to use some sub-protocols for this, but I
+              did not see any written in Erlang.<br>
+              <br>
+            </div>
+            So, I would like to ask you, do I understand right that
+            Cowboy does not have this feature too? If so, do you have
+            some idea how can I implement a basic request-response
+            mechanism? Probably one of you guys in this forum have some
+            idea.<br>
+            <br>
+          </div>
+          <div>Btw, the links I read about this topic:<br>
+            Â Â Â  <a href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol" target="_blank">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>
+            Â Â Â  <a href="http://alabor.me/articles/request-response-oriented-websockets/" target="_blank">http://alabor.me/articles/request-response-oriented-websockets/</a><br>
+            Â Â Â  <a href="https://www.npmjs.com/package/primus-responder" target="_blank">https://www.npmjs.com/package/primus-responder</a><br>
+          </div>
+          <div><br>
+          </div>
+          thanks for your help,<br>
+        </div>
+        /Robi<br>
+      </div>
+      <br>
+      <fieldset></fieldset>
+      <br>
+      </div></div><span class=""><pre>_______________________________________________
+Extend mailing list
+<a href="mailto:Extend@lists.ninenines.eu" target="_blank">Extend@lists.ninenines.eu</a>
+<a href="https://lists.ninenines.eu/listinfo/extend" target="_blank">https://lists.ninenines.eu/listinfo/extend</a>
+</pre>
+    </span></blockquote>
+    <br>
+  </div>
+
+</blockquote></div><br></div>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/b67122b6/attachment-0001.html b/_build/static/archives/extend/attachments/20150624/b67122b6/attachment-0001.html new file mode 100644 index 00000000..906afb56 --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/b67122b6/attachment-0001.html @@ -0,0 +1,77 @@ + +<html>
+  <head>
+    <meta content="text/html; charset=windows-1252"
+      http-equiv="Content-Type">
+  </head>
+  <body bgcolor="#FFFFFF" text="#000000">
+    hello Robi,<br>
+    <br>
+    you might be interested in erwa:<br>
+    <a class="moz-txt-link-freetext" href="https://github.com/bwegh/erwa">https://github.com/bwegh/erwa</a><br>
+    <br>
+    Cheers,<br>
+    Bas<br>
+    <br>
+    <div class="moz-cite-prefix">On 06/24/2015 11:18 AM, Robert Balogh
+      wrote:<br>
+    </div>
+    <blockquote
+cite="mid:CAA4OwwXkFLY0pO7qudu4Xhe-aD4=wYGoitYx=NtN6dh5GN25CA@mail.gmail.com"
+      type="cite">
+      <div dir="ltr">
+        <div>
+          <div>
+            <div>
+              <div>hello,<br>
+                <br>
+              </div>
+              According to you grate support I got from you at
+              yesterday, I could continue my project, where I use Cowboy
+              webserver and using Websocket. Now I made an own web page
+              with basic features I need, so the server and client can
+              communicates to eachother. I like it. <br>
+              <br>
+              Now I would like to step forward, and I would like to
+              implement a Request-Response mechanism. I read few
+              articles in to this topic, and all of them has mentioned
+              this "feature" is not part of the Websocket standard. They
+              were suggested to use some sub-protocols for this, but I
+              did not see any written in Erlang.<br>
+              <br>
+            </div>
+            So, I would like to ask you, do I understand right that
+            Cowboy does not have this feature too? If so, do you have
+            some idea how can I implement a basic request-response
+            mechanism? Probably one of you guys in this forum have some
+            idea.<br>
+            <br>
+          </div>
+          <div>Btw, the links I read about this topic:<br>
+                <a moz-do-not-send="true"
+href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>
+                <a moz-do-not-send="true"
+              href="http://alabor.me/articles/request-response-oriented-websockets/">http://alabor.me/articles/request-response-oriented-websockets/</a><br>
+                <a moz-do-not-send="true"
+              href="https://www.npmjs.com/package/primus-responder">https://www.npmjs.com/package/primus-responder</a><br>
+          </div>
+          <div><br>
+          </div>
+          thanks for your help,<br>
+        </div>
+        /Robi<br>
+      </div>
+      <br>
+      <fieldset class="mimeAttachmentHeader"></fieldset>
+      <br>
+      <pre wrap="">_______________________________________________
+Extend mailing list
+<a class="moz-txt-link-abbreviated" href="mailto:Extend@lists.ninenines.eu">Extend@lists.ninenines.eu</a>
+<a class="moz-txt-link-freetext" href="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</a>
+</pre>
+    </blockquote>
+    <br>
+  </body>
+</html>
+ + diff --git a/_build/static/archives/extend/attachments/20150624/b67122b6/attachment.html b/_build/static/archives/extend/attachments/20150624/b67122b6/attachment.html new file mode 100644 index 00000000..906afb56 --- /dev/null +++ b/_build/static/archives/extend/attachments/20150624/b67122b6/attachment.html @@ -0,0 +1,77 @@ + +<html>
+  <head>
+    <meta content="text/html; charset=windows-1252"
+      http-equiv="Content-Type">
+  </head>
+  <body bgcolor="#FFFFFF" text="#000000">
+    hello Robi,<br>
+    <br>
+    you might be interested in erwa:<br>
+    <a class="moz-txt-link-freetext" href="https://github.com/bwegh/erwa">https://github.com/bwegh/erwa</a><br>
+    <br>
+    Cheers,<br>
+    Bas<br>
+    <br>
+    <div class="moz-cite-prefix">On 06/24/2015 11:18 AM, Robert Balogh
+      wrote:<br>
+    </div>
+    <blockquote
+cite="mid:CAA4OwwXkFLY0pO7qudu4Xhe-aD4=wYGoitYx=NtN6dh5GN25CA@mail.gmail.com"
+      type="cite">
+      <div dir="ltr">
+        <div>
+          <div>
+            <div>
+              <div>hello,<br>
+                <br>
+              </div>
+              According to you grate support I got from you at
+              yesterday, I could continue my project, where I use Cowboy
+              webserver and using Websocket. Now I made an own web page
+              with basic features I need, so the server and client can
+              communicates to eachother. I like it. <br>
+              <br>
+              Now I would like to step forward, and I would like to
+              implement a Request-Response mechanism. I read few
+              articles in to this topic, and all of them has mentioned
+              this "feature" is not part of the Websocket standard. They
+              were suggested to use some sub-protocols for this, but I
+              did not see any written in Erlang.<br>
+              <br>
+            </div>
+            So, I would like to ask you, do I understand right that
+            Cowboy does not have this feature too? If so, do you have
+            some idea how can I implement a basic request-response
+            mechanism? Probably one of you guys in this forum have some
+            idea.<br>
+            <br>
+          </div>
+          <div>Btw, the links I read about this topic:<br>
+                <a moz-do-not-send="true"
+href="http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol">http://stackoverflow.com/questions/10882370/websocket-request-response-subprotocol</a><br>
+                <a moz-do-not-send="true"
+              href="http://alabor.me/articles/request-response-oriented-websockets/">http://alabor.me/articles/request-response-oriented-websockets/</a><br>
+                <a moz-do-not-send="true"
+              href="https://www.npmjs.com/package/primus-responder">https://www.npmjs.com/package/primus-responder</a><br>
+          </div>
+          <div><br>
+          </div>
+          thanks for your help,<br>
+        </div>
+        /Robi<br>
+      </div>
+      <br>
+      <fieldset class="mimeAttachmentHeader"></fieldset>
+      <br>
+      <pre wrap="">_______________________________________________
+Extend mailing list
+<a class="moz-txt-link-abbreviated" href="mailto:Extend@lists.ninenines.eu">Extend@lists.ninenines.eu</a>
+<a class="moz-txt-link-freetext" href="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</a>
+</pre>
+    </blockquote>
+    <br>
+  </body>
+</html>
+ + -- cgit v1.2.3