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 --- archives/extend/2013-January/000028.html | 133 +++++++++++++++++ archives/extend/2013-January/000029.html | 154 +++++++++++++++++++ archives/extend/2013-January/000030.html | 175 ++++++++++++++++++++++ archives/extend/2013-January/000031.html | 212 +++++++++++++++++++++++++++ archives/extend/2013-January/000032.html | 236 ++++++++++++++++++++++++++++++ archives/extend/2013-January/000033.html | 77 ++++++++++ archives/extend/2013-January/000034.html | 79 ++++++++++ archives/extend/2013-January/000035.html | 79 ++++++++++ archives/extend/2013-January/000036.html | 80 ++++++++++ archives/extend/2013-January/000037.html | 74 ++++++++++ archives/extend/2013-January/000038.html | 86 +++++++++++ archives/extend/2013-January/000039.html | 90 ++++++++++++ archives/extend/2013-January/000040.html | 77 ++++++++++ archives/extend/2013-January/000041.html | 112 ++++++++++++++ archives/extend/2013-January/000042.html | 92 ++++++++++++ archives/extend/2013-January/author.html | 122 +++++++++++++++ archives/extend/2013-January/date.html | 122 +++++++++++++++ archives/extend/2013-January/index.html | 151 +++++++++++++++++++ archives/extend/2013-January/subject.html | 122 +++++++++++++++ archives/extend/2013-January/thread.html | 151 +++++++++++++++++++ 20 files changed, 2424 insertions(+) create mode 100644 archives/extend/2013-January/000028.html create mode 100644 archives/extend/2013-January/000029.html create mode 100644 archives/extend/2013-January/000030.html create mode 100644 archives/extend/2013-January/000031.html create mode 100644 archives/extend/2013-January/000032.html create mode 100644 archives/extend/2013-January/000033.html create mode 100644 archives/extend/2013-January/000034.html create mode 100644 archives/extend/2013-January/000035.html create mode 100644 archives/extend/2013-January/000036.html create mode 100644 archives/extend/2013-January/000037.html create mode 100644 archives/extend/2013-January/000038.html create mode 100644 archives/extend/2013-January/000039.html create mode 100644 archives/extend/2013-January/000040.html create mode 100644 archives/extend/2013-January/000041.html create mode 100644 archives/extend/2013-January/000042.html create mode 100644 archives/extend/2013-January/author.html create mode 100644 archives/extend/2013-January/date.html create mode 100644 archives/extend/2013-January/index.html create mode 100644 archives/extend/2013-January/subject.html create mode 100644 archives/extend/2013-January/thread.html (limited to 'archives/extend/2013-January') diff --git a/archives/extend/2013-January/000028.html b/archives/extend/2013-January/000028.html new file mode 100644 index 00000000..8205944b --- /dev/null +++ b/archives/extend/2013-January/000028.html @@ -0,0 +1,133 @@ + + + + [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released + + + + + + + + + + +

[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released

+ Max Lapshin + max.lapshin at gmail.com +
+ Thu Jan 3 10:30:30 CET 2013 +

+
+ +
Loic, it would be great to hear a bit, what problems have you met with.
+
+What issues with stability can be in acceptor pool?
+
+Also I have question about updating protocol options: have you done
+something with the problem that after updating protocol options existing
+workers are running with old config?
+
+On Tuesday, December 25, 2012, Loïc Hoguin wrote:
+
+> Ho ho ho!
+>
+> I have just tagged version 0.6.0 of the Ranch project!
+>
+> Ranch is a socket acceptor pool for TCP protocols.
+>
+>   https://github.com/extend/**ranch <https://github.com/extend/ranch>
+>
+> Ranch is used by the next version of Cowboy, 0.8.0, set to be released
+> early February, but also in Basho's Riak multi-data center replication
+> amongst others.
+>
+> All tickets have been resolved. A significant contribution was made by
+> Andrew Majorov to improve the fault tolerance capabilities of the
+> application, making sure it always restarts properly when things go wrong.
+> This has been made possible thanks to the amazing project from Daniel Luna,
+> chaos_monkey (https://github.com/dluna/**chaos_monkey<https://github.com/dluna/chaos_monkey>
+> ).
+>
+> The guide has also been improved and completed.
+>
+>   http://ninenines.eu/docs/en/**ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction>
+>
+> If the guide isn't enough, drop by our new IRC channel dedicated to
+> Cowboy, Ranch and all our other projects! #ninenines on Freenode.
+>
+> Following is the list of change since last time:
+>
+>  *  Improve fault tolerance thanks to chaos_monkey testing
+>  *  Add 'nodelay' option to transports
+>  *  Add 'verify' option to ranch_ssl transport
+>  *  Add 'socket' option to pass an already open socket to the listener
+>  *  Add Transport:sendfile/2 function (uses a fallback if unavailable)
+>  *  Allow IP tuples in Transport:connect/3
+>  *  Add ranch:set_max_connections/2 to update the value live
+>  *  Add ranch:get_max_connections/1 to retrieve it
+>
+> We are always looking for feedback, especially now that there is no ticket
+> left open on this project. If you are using Ranch and have questions or
+> needs that it doesn't cover, please send them to us.
+>
+> Commercial support will be available starting from January, ping me if you
+> are interested. Details will be announced at a later time on the
+> ninenines.eu mailing list.
+>
+> I want to thank all contributors for helping this project by opening
+> tickets, sending patches and offering feedback. I am as always very
+> grateful for any and all contributions. I wouldn't have made it this far
+> without the tremendous help I receive everyday.
+>
+> Thanks to all and have a nice holiday!
+>
+> --
+> Loïc Hoguin
+> Erlang Santa
+> Nine Nines
+> http://ninenines.eu
+> ______________________________**_________________
+> erlang-questions mailing list
+> erlang-questions at erlang.org
+> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130103/bae06e70/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000029.html b/archives/extend/2013-January/000029.html new file mode 100644 index 00000000..8f69dfb4 --- /dev/null +++ b/archives/extend/2013-January/000029.html @@ -0,0 +1,154 @@ + + + + [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released + + + + + + + + + + +

[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Jan 3 13:46:56 CET 2013 +

+
+ +
Haven't had any stability issue. What we did here is ensure that when 
+any process gets killed for any reason, especially reasons we can't 
+foresee, Ranch continues to work as expected.
+
+Ranch not updating protocol options for existing connections isn't a 
+problem, it won't be "fixed". Ranch can't guess how connection processes 
+are implemented. It's up to you to allow this if you need it. The 
+upgrade updates the options for all acceptors and all future 
+connections, that's it.
+
+On 01/03/2013 10:30 AM, Max Lapshin wrote:
+> Loic, it would be great to hear a bit, what problems have you met with.
+>
+> What issues with stability can be in acceptor pool?
+>
+> Also I have question about updating protocol options: have you done
+> something with the problem that after updating protocol options existing
+> workers are running with old config?
+>
+> On Tuesday, December 25, 2012, Loïc Hoguin wrote:
+>
+>     Ho ho ho!
+>
+>     I have just tagged version 0.6.0 of the Ranch project!
+>
+>     Ranch is a socket acceptor pool for TCP protocols.
+>
+>     https://github.com/extend/__ranch <https://github.com/extend/ranch>
+>
+>     Ranch is used by the next version of Cowboy, 0.8.0, set to be
+>     released early February, but also in Basho's Riak multi-data center
+>     replication amongst others.
+>
+>     All tickets have been resolved. A significant contribution was made
+>     by Andrew Majorov to improve the fault tolerance capabilities of the
+>     application, making sure it always restarts properly when things go
+>     wrong. This has been made possible thanks to the amazing project
+>     from Daniel Luna, chaos_monkey
+>     (https://github.com/dluna/__chaos_monkey
+>     <https://github.com/dluna/chaos_monkey>).
+>
+>     The guide has also been improved and completed.
+>
+>     http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction
+>     <http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction>
+>
+>     If the guide isn't enough, drop by our new IRC channel dedicated to
+>     Cowboy, Ranch and all our other projects! #ninenines on Freenode.
+>
+>     Following is the list of change since last time:
+>
+>       *  Improve fault tolerance thanks to chaos_monkey testing
+>       *  Add 'nodelay' option to transports
+>       *  Add 'verify' option to ranch_ssl transport
+>       *  Add 'socket' option to pass an already open socket to the listener
+>       *  Add Transport:sendfile/2 function (uses a fallback if unavailable)
+>       *  Allow IP tuples in Transport:connect/3
+>       *  Add ranch:set_max_connections/2 to update the value live
+>       *  Add ranch:get_max_connections/1 to retrieve it
+>
+>     We are always looking for feedback, especially now that there is no
+>     ticket left open on this project. If you are using Ranch and have
+>     questions or needs that it doesn't cover, please send them to us.
+>
+>     Commercial support will be available starting from January, ping me
+>     if you are interested. Details will be announced at a later time on
+>     the ninenines.eu <http://ninenines.eu> mailing list.
+>
+>     I want to thank all contributors for helping this project by opening
+>     tickets, sending patches and offering feedback. I am as always very
+>     grateful for any and all contributions. I wouldn't have made it this
+>     far without the tremendous help I receive everyday.
+>
+>     Thanks to all and have a nice holiday!
+>
+>     --
+>     Loïc Hoguin
+>     Erlang Santa
+>     Nine Nines
+>     http://ninenines.eu
+>     _________________________________________________
+>     erlang-questions mailing list
+>     erlang-questions at erlang.org
+>     http://erlang.org/mailman/__listinfo/erlang-questions
+>     <http://erlang.org/mailman/listinfo/erlang-questions>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000030.html b/archives/extend/2013-January/000030.html new file mode 100644 index 00000000..c75a7032 --- /dev/null +++ b/archives/extend/2013-January/000030.html @@ -0,0 +1,175 @@ + + + + [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released + + + + + + + + + + +

[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released

+ Max Lapshin + max.lapshin at gmail.com +
+ Thu Jan 3 14:32:16 CET 2013 +

+
+ +
I mean situation that after cowboy:update_options existing acceptors are
+still working with old routes.
+Currently it is useless API, so I have to stop cowboy and start it back.
+
+
+On Thu, Jan 3, 2013 at 4:46 PM, Loïc Hoguin <essen at ninenines.eu> wrote:
+
+> Haven't had any stability issue. What we did here is ensure that when any
+> process gets killed for any reason, especially reasons we can't foresee,
+> Ranch continues to work as expected.
+>
+> Ranch not updating protocol options for existing connections isn't a
+> problem, it won't be "fixed". Ranch can't guess how connection processes
+> are implemented. It's up to you to allow this if you need it. The upgrade
+> updates the options for all acceptors and all future connections, that's it.
+>
+>
+> On 01/03/2013 10:30 AM, Max Lapshin wrote:
+>
+>> Loic, it would be great to hear a bit, what problems have you met with.
+>>
+>> What issues with stability can be in acceptor pool?
+>>
+>> Also I have question about updating protocol options: have you done
+>> something with the problem that after updating protocol options existing
+>> workers are running with old config?
+>>
+>> On Tuesday, December 25, 2012, Loïc Hoguin wrote:
+>>
+>>     Ho ho ho!
+>>
+>>     I have just tagged version 0.6.0 of the Ranch project!
+>>
+>>     Ranch is a socket acceptor pool for TCP protocols.
+>>
+>>     https://github.com/extend/__**ranch<https://github.com/extend/__ranch><
+>> https://github.com/extend/**ranch <https://github.com/extend/ranch>>
+>>
+>>
+>>     Ranch is used by the next version of Cowboy, 0.8.0, set to be
+>>     released early February, but also in Basho's Riak multi-data center
+>>     replication amongst others.
+>>
+>>     All tickets have been resolved. A significant contribution was made
+>>     by Andrew Majorov to improve the fault tolerance capabilities of the
+>>     application, making sure it always restarts properly when things go
+>>     wrong. This has been made possible thanks to the amazing project
+>>     from Daniel Luna, chaos_monkey
+>>     (https://github.com/dluna/__**chaos_monkey<https://github.com/dluna/__chaos_monkey>
+>>     <https://github.com/dluna/**chaos_monkey<https://github.com/dluna/chaos_monkey>
+>> >).
+>>
+>>
+>>     The guide has also been improved and completed.
+>>
+>>     http://ninenines.eu/docs/en/__**ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction>
+>>
+>>     <http://ninenines.eu/docs/en/**ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction>
+>> >
+>>
+>>     If the guide isn't enough, drop by our new IRC channel dedicated to
+>>     Cowboy, Ranch and all our other projects! #ninenines on Freenode.
+>>
+>>     Following is the list of change since last time:
+>>
+>>       *  Improve fault tolerance thanks to chaos_monkey testing
+>>       *  Add 'nodelay' option to transports
+>>       *  Add 'verify' option to ranch_ssl transport
+>>       *  Add 'socket' option to pass an already open socket to the
+>> listener
+>>       *  Add Transport:sendfile/2 function (uses a fallback if
+>> unavailable)
+>>       *  Allow IP tuples in Transport:connect/3
+>>       *  Add ranch:set_max_connections/2 to update the value live
+>>       *  Add ranch:get_max_connections/1 to retrieve it
+>>
+>>     We are always looking for feedback, especially now that there is no
+>>     ticket left open on this project. If you are using Ranch and have
+>>     questions or needs that it doesn't cover, please send them to us.
+>>
+>>     Commercial support will be available starting from January, ping me
+>>     if you are interested. Details will be announced at a later time on
+>>     the ninenines.eu <http://ninenines.eu> mailing list.
+>>
+>>
+>>     I want to thank all contributors for helping this project by opening
+>>     tickets, sending patches and offering feedback. I am as always very
+>>     grateful for any and all contributions. I wouldn't have made it this
+>>     far without the tremendous help I receive everyday.
+>>
+>>     Thanks to all and have a nice holiday!
+>>
+>>     --
+>>     Loïc Hoguin
+>>     Erlang Santa
+>>     Nine Nines
+>>     http://ninenines.eu
+>>     ______________________________**___________________
+>>     erlang-questions mailing list
+>>     erlang-questions at erlang.org
+>>     http://erlang.org/mailman/__**listinfo/erlang-questions<http://erlang.org/mailman/__listinfo/erlang-questions>
+>>     <http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
+>> >
+>>
+>>
+>
+> --
+> Loïc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130103/f6c7fd25/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000031.html b/archives/extend/2013-January/000031.html new file mode 100644 index 00000000..e62e78e1 --- /dev/null +++ b/archives/extend/2013-January/000031.html @@ -0,0 +1,212 @@ + + + + [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released + + + + + + + + + + +

[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Jan 3 14:51:48 CET 2013 +

+
+ +
Existing acceptors were using the old options for the next connection 
+and then switched to the new options. But that has been fixed a long 
+time ago. Ranch doesn't have that issue.
+
+On 01/03/2013 02:32 PM, Max Lapshin wrote:
+> I mean situation that after cowboy:update_options existing acceptors are
+> still working with old routes.
+> Currently it is useless API, so I have to stop cowboy and start it back.
+>
+>
+> On Thu, Jan 3, 2013 at 4:46 PM, Loïc Hoguin <essen at ninenines.eu
+> <mailto:essen at ninenines.eu>> wrote:
+>
+>     Haven't had any stability issue. What we did here is ensure that
+>     when any process gets killed for any reason, especially reasons we
+>     can't foresee, Ranch continues to work as expected.
+>
+>     Ranch not updating protocol options for existing connections isn't a
+>     problem, it won't be "fixed". Ranch can't guess how connection
+>     processes are implemented. It's up to you to allow this if you need
+>     it. The upgrade updates the options for all acceptors and all future
+>     connections, that's it.
+>
+>
+>     On 01/03/2013 10:30 AM, Max Lapshin wrote:
+>
+>         Loic, it would be great to hear a bit, what problems have you
+>         met with.
+>
+>         What issues with stability can be in acceptor pool?
+>
+>         Also I have question about updating protocol options: have you done
+>         something with the problem that after updating protocol options
+>         existing
+>         workers are running with old config?
+>
+>         On Tuesday, December 25, 2012, Loïc Hoguin wrote:
+>
+>              Ho ho ho!
+>
+>              I have just tagged version 0.6.0 of the Ranch project!
+>
+>              Ranch is a socket acceptor pool for TCP protocols.
+>
+>         https://github.com/extend/____ranch
+>         <https://github.com/extend/__ranch>
+>         <https://github.com/extend/__ranch
+>         <https://github.com/extend/ranch>>
+>
+>
+>              Ranch is used by the next version of Cowboy, 0.8.0, set to be
+>              released early February, but also in Basho's Riak
+>         multi-data center
+>              replication amongst others.
+>
+>              All tickets have been resolved. A significant contribution
+>         was made
+>              by Andrew Majorov to improve the fault tolerance
+>         capabilities of the
+>              application, making sure it always restarts properly when
+>         things go
+>              wrong. This has been made possible thanks to the amazing
+>         project
+>              from Daniel Luna, chaos_monkey
+>              (https://github.com/dluna/____chaos_monkey
+>         <https://github.com/dluna/__chaos_monkey>
+>              <https://github.com/dluna/__chaos_monkey
+>         <https://github.com/dluna/chaos_monkey>>).
+>
+>
+>              The guide has also been improved and completed.
+>
+>         http://ninenines.eu/docs/en/____ranch/HEAD/guide/introduction
+>         <http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction>
+>
+>
+>         <http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction
+>         <http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction>>
+>
+>              If the guide isn't enough, drop by our new IRC channel
+>         dedicated to
+>              Cowboy, Ranch and all our other projects! #ninenines on
+>         Freenode.
+>
+>              Following is the list of change since last time:
+>
+>                *  Improve fault tolerance thanks to chaos_monkey testing
+>                *  Add 'nodelay' option to transports
+>                *  Add 'verify' option to ranch_ssl transport
+>                *  Add 'socket' option to pass an already open socket to
+>         the listener
+>                *  Add Transport:sendfile/2 function (uses a fallback if
+>         unavailable)
+>                *  Allow IP tuples in Transport:connect/3
+>                *  Add ranch:set_max_connections/2 to update the value live
+>                *  Add ranch:get_max_connections/1 to retrieve it
+>
+>              We are always looking for feedback, especially now that
+>         there is no
+>              ticket left open on this project. If you are using Ranch
+>         and have
+>              questions or needs that it doesn't cover, please send them
+>         to us.
+>
+>              Commercial support will be available starting from January,
+>         ping me
+>              if you are interested. Details will be announced at a later
+>         time on
+>              the ninenines.eu <http://ninenines.eu>
+>         <http://ninenines.eu> mailing list.
+>
+>
+>              I want to thank all contributors for helping this project
+>         by opening
+>              tickets, sending patches and offering feedback. I am as
+>         always very
+>              grateful for any and all contributions. I wouldn't have
+>         made it this
+>              far without the tremendous help I receive everyday.
+>
+>              Thanks to all and have a nice holiday!
+>
+>              --
+>              Loïc Hoguin
+>              Erlang Santa
+>              Nine Nines
+>         http://ninenines.eu
+>              ___________________________________________________
+>              erlang-questions mailing list
+>         erlang-questions at erlang.org <mailto:erlang-questions at erlang.org>
+>         http://erlang.org/mailman/____listinfo/erlang-questions
+>         <http://erlang.org/mailman/__listinfo/erlang-questions>
+>              <http://erlang.org/mailman/__listinfo/erlang-questions
+>         <http://erlang.org/mailman/listinfo/erlang-questions>>
+>
+>
+>
+>     --
+>     Loïc Hoguin
+>     Erlang Cowboy
+>     Nine Nines
+>     http://ninenines.eu
+>
+>
+
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000032.html b/archives/extend/2013-January/000032.html new file mode 100644 index 00000000..814279e3 --- /dev/null +++ b/archives/extend/2013-January/000032.html @@ -0,0 +1,236 @@ + + + + [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released + + + + + + + + + + +

[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released

+ Max Lapshin + max.lapshin at gmail.com +
+ Thu Jan 3 15:00:56 CET 2013 +

+
+ +
ok
+
+
+On Thu, Jan 3, 2013 at 5:51 PM, Loïc Hoguin <essen at ninenines.eu> wrote:
+
+> Existing acceptors were using the old options for the next connection and
+> then switched to the new options. But that has been fixed a long time ago.
+> Ranch doesn't have that issue.
+>
+>
+> On 01/03/2013 02:32 PM, Max Lapshin wrote:
+>
+>> I mean situation that after cowboy:update_options existing acceptors are
+>> still working with old routes.
+>> Currently it is useless API, so I have to stop cowboy and start it back.
+>>
+>>
+>> On Thu, Jan 3, 2013 at 4:46 PM, Loïc Hoguin <essen at ninenines.eu
+>> <mailto:essen at ninenines.eu>> wrote:
+>>
+>>     Haven't had any stability issue. What we did here is ensure that
+>>     when any process gets killed for any reason, especially reasons we
+>>     can't foresee, Ranch continues to work as expected.
+>>
+>>     Ranch not updating protocol options for existing connections isn't a
+>>     problem, it won't be "fixed". Ranch can't guess how connection
+>>     processes are implemented. It's up to you to allow this if you need
+>>     it. The upgrade updates the options for all acceptors and all future
+>>     connections, that's it.
+>>
+>>
+>>     On 01/03/2013 10:30 AM, Max Lapshin wrote:
+>>
+>>         Loic, it would be great to hear a bit, what problems have you
+>>         met with.
+>>
+>>         What issues with stability can be in acceptor pool?
+>>
+>>         Also I have question about updating protocol options: have you
+>> done
+>>         something with the problem that after updating protocol options
+>>         existing
+>>         workers are running with old config?
+>>
+>>         On Tuesday, December 25, 2012, Loïc Hoguin wrote:
+>>
+>>              Ho ho ho!
+>>
+>>              I have just tagged version 0.6.0 of the Ranch project!
+>>
+>>              Ranch is a socket acceptor pool for TCP protocols.
+>>
+>>         https://github.com/extend/____**ranch<https://github.com/extend/____ranch>
+>>         <https://github.com/extend/__**ranch<https://github.com/extend/__ranch>
+>> >
+>>
+>>         <https://github.com/extend/__**ranch<https://github.com/extend/__ranch>
+>>         <https://github.com/extend/**ranch<https://github.com/extend/ranch>
+>> >>
+>>
+>>
+>>              Ranch is used by the next version of Cowboy, 0.8.0, set to be
+>>              released early February, but also in Basho's Riak
+>>         multi-data center
+>>              replication amongst others.
+>>
+>>              All tickets have been resolved. A significant contribution
+>>         was made
+>>              by Andrew Majorov to improve the fault tolerance
+>>         capabilities of the
+>>              application, making sure it always restarts properly when
+>>         things go
+>>              wrong. This has been made possible thanks to the amazing
+>>         project
+>>              from Daniel Luna, chaos_monkey
+>>              (https://github.com/dluna/____**chaos_monkey<https://github.com/dluna/____chaos_monkey>
+>>         <https://github.com/dluna/__**chaos_monkey<https://github.com/dluna/__chaos_monkey>
+>> >
+>>
+>>              <https://github.com/dluna/__**chaos_monkey<https://github.com/dluna/__chaos_monkey>
+>>         <https://github.com/dluna/**chaos_monkey<https://github.com/dluna/chaos_monkey>
+>> >>).
+>>
+>>
+>>              The guide has also been improved and completed.
+>>
+>>         http://ninenines.eu/docs/en/__**__ranch/HEAD/guide/**introduction<http://ninenines.eu/docs/en/____ranch/HEAD/guide/introduction>
+>>         <http://ninenines.eu/docs/en/_**_ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction>
+>> **>
+>>
+>>
+>>
+>>         <http://ninenines.eu/docs/en/_**_ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction>
+>>         <http://ninenines.eu/docs/en/**ranch/HEAD/guide/introduction<http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction>
+>> >**>
+>>
+>>              If the guide isn't enough, drop by our new IRC channel
+>>         dedicated to
+>>              Cowboy, Ranch and all our other projects! #ninenines on
+>>         Freenode.
+>>
+>>              Following is the list of change since last time:
+>>
+>>                *  Improve fault tolerance thanks to chaos_monkey testing
+>>                *  Add 'nodelay' option to transports
+>>                *  Add 'verify' option to ranch_ssl transport
+>>                *  Add 'socket' option to pass an already open socket to
+>>         the listener
+>>                *  Add Transport:sendfile/2 function (uses a fallback if
+>>         unavailable)
+>>                *  Allow IP tuples in Transport:connect/3
+>>                *  Add ranch:set_max_connections/2 to update the value live
+>>                *  Add ranch:get_max_connections/1 to retrieve it
+>>
+>>              We are always looking for feedback, especially now that
+>>         there is no
+>>              ticket left open on this project. If you are using Ranch
+>>         and have
+>>              questions or needs that it doesn't cover, please send them
+>>         to us.
+>>
+>>              Commercial support will be available starting from January,
+>>         ping me
+>>              if you are interested. Details will be announced at a later
+>>         time on
+>>              the ninenines.eu <http://ninenines.eu>
+>>         <http://ninenines.eu> mailing list.
+>>
+>>
+>>              I want to thank all contributors for helping this project
+>>         by opening
+>>              tickets, sending patches and offering feedback. I am as
+>>         always very
+>>              grateful for any and all contributions. I wouldn't have
+>>         made it this
+>>              far without the tremendous help I receive everyday.
+>>
+>>              Thanks to all and have a nice holiday!
+>>
+>>              --
+>>              Loïc Hoguin
+>>              Erlang Santa
+>>              Nine Nines
+>>         http://ninenines.eu
+>>              ______________________________**_____________________
+>>              erlang-questions mailing list
+>>         erlang-questions at erlang.org <mailto:erlang-questions@**erlang.org<erlang-questions at erlang.org>
+>> >
+>>         http://erlang.org/mailman/____**listinfo/erlang-questions<http://erlang.org/mailman/____listinfo/erlang-questions>
+>>         <http://erlang.org/mailman/__**listinfo/erlang-questions<http://erlang.org/mailman/__listinfo/erlang-questions>
+>> >
+>>
+>>              <http://erlang.org/mailman/__**listinfo/erlang-questions<http://erlang.org/mailman/__listinfo/erlang-questions>
+>>         <http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
+>> >>
+>>
+>>
+>>
+>>     --
+>>     Loïc Hoguin
+>>     Erlang Cowboy
+>>     Nine Nines
+>>     http://ninenines.eu
+>>
+>>
+>>
+>
+> --
+> Loïc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130103/d9dbc1a5/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000033.html b/archives/extend/2013-January/000033.html new file mode 100644 index 00000000..2967e683 --- /dev/null +++ b/archives/extend/2013-January/000033.html @@ -0,0 +1,77 @@ + + + + [99s-extend] Call for testers: middleware support + + + + + + + + + + +

[99s-extend] Call for testers: middleware support

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Jan 3 22:52:46 CET 2013 +

+
+ +
Hello!
+
+Been a year. How' ya been?
+
+Added middleware support. Probably broke things. Please test and open 
+tickets if I did?
+
+https://github.com/extend/cowboy/commit/1b3f510b7e8d5413901ba72adfe361773f3e9097
+
+Thanks.
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000034.html b/archives/extend/2013-January/000034.html new file mode 100644 index 00000000..058aedb0 --- /dev/null +++ b/archives/extend/2013-January/000034.html @@ -0,0 +1,79 @@ + + + + [99s-extend] Call for testers: middleware support + + + + + + + + + + +

[99s-extend] Call for testers: middleware support

+ Thomas Allen + thomas at oinksoft.com +
+ Fri Jan 4 15:31:21 CET 2013 +

+
+ +
Thank you Löic, this looks much cleaner than what I've used in its place.
+
+Thomas
+
+
+On 01/03/2013 04:52 PM, Loïc Hoguin wrote:
+> Hello!
+>
+> Been a year. How' ya been?
+>
+> Added middleware support. Probably broke things. Please test and open
+> tickets if I did?
+>
+> https://github.com/extend/cowboy/commit/1b3f510b7e8d5413901ba72adfe361773f3e9097
+>
+>
+> Thanks.
+>
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000035.html b/archives/extend/2013-January/000035.html new file mode 100644 index 00000000..0bc878fc --- /dev/null +++ b/archives/extend/2013-January/000035.html @@ -0,0 +1,79 @@ + + + + [99s-extend] Cowboy, how call my database select function + + + + + + + + + + +

[99s-extend] Cowboy, how call my database select function

+ Козлов Вячеслав + kozlov-ter at yandex.ru +
+ Tue Jan 8 22:36:56 CET 2013 +

+
+ +
Hello!
+Prompt please, beginning to study the Erlang.
+I have a library for working with ЕRedis.
+Plugged it into the project Cowboy with the help of Rebar.
+After the launch of a Cowboy through the script in the console ERL, I see that the function (eredis_db:get_script) is  works and I get the desired result:
+
+EDB R15B03 (erts-5.9.3.1) [source] [async-threads:0] [hipe] [kernel-poll:false]
+Eshell V5.9.3.1 (abort with ^G)
+1> eredis_db:get_script("example", "test").
+
+Tell me how can I use this function in a Cowboy, in hendlers.
+I hope I could explain clearly.
+-- 
+Engineer CAM 
+Vyacheslav Kozlov 
+LLC "TER" 
+http://www.ter-energo.ru
+tel.+7910909xxxx
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000036.html b/archives/extend/2013-January/000036.html new file mode 100644 index 00000000..4a9db14c --- /dev/null +++ b/archives/extend/2013-January/000036.html @@ -0,0 +1,80 @@ + + + + [99s-extend] Cowboy, how call my database select function + + + + + + + + + + +

[99s-extend] Cowboy, how call my database select function

+ Thomas Allen + thomas at oinksoft.com +
+ Wed Jan 9 00:12:02 CET 2013 +

+
+ +
On 1/8/13 4:36 PM, Козлов Вячеслав wrote:
+> I hope I could explain clearly.
+
+This was not quite clear to me, but I'll do my best.
+
+> Tell me how can I use this function in a Cowboy, in hendlers.
+
+Well, you'd use it like any other Erlang function. If it's in a handler, 
+you probably want to use init/3 or handle/2:
+
+handle(Req, State) ->
+     _EredisScript = eredis_db:get_script("example", "test"),
+     {ok, Resp} = cowboy_req:reply(200, Req),
+     {ok, Resp, State}.
+
+See other examples of implementing `cowboy_http_handler' behaviour in 
+the Cowboy documentation and in the examples included with the library.
+
+Thomas Allen
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000037.html b/archives/extend/2013-January/000037.html new file mode 100644 index 00000000..098c5631 --- /dev/null +++ b/archives/extend/2013-January/000037.html @@ -0,0 +1,74 @@ + + + + [99s-extend] [ANN] Ranch 0.6.1 + + + + + + + + + + +

[99s-extend] [ANN] Ranch 0.6.1

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Jan 17 19:33:26 CET 2013 +

+
+ +
Short, quick and semi-private announcement: Ranch 0.6.1 has been tagged.
+
+It includes a few guide updates, the addition of the raw option for 
+specifying platform-specific socket options, and performance 
+improvements when using the {max_connections, infinity} option.
+
+Enjoy!
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000038.html b/archives/extend/2013-January/000038.html new file mode 100644 index 00000000..64343529 --- /dev/null +++ b/archives/extend/2013-January/000038.html @@ -0,0 +1,86 @@ + + + + [99s-extend] [ANN] Ranch 0.6.1 + + + + + + + + + + +

[99s-extend] [ANN] Ranch 0.6.1

+ Jeremy Ong + jeremy at quarkgames.com +
+ Thu Jan 17 20:42:38 CET 2013 +

+
+ +
Thanks Loïc!
+
+
+On Thu, Jan 17, 2013 at 10:33 AM, Loïc Hoguin <essen at ninenines.eu> wrote:
+
+> Short, quick and semi-private announcement: Ranch 0.6.1 has been tagged.
+>
+> It includes a few guide updates, the addition of the raw option for
+> specifying platform-specific socket options, and performance improvements
+> when using the {max_connections, infinity} option.
+>
+> Enjoy!
+>
+> --
+> Loïc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+> ______________________________**_________________
+> Extend mailing list
+> Extend at lists.ninenines.eu
+> http://lists.ninenines.eu:81/**listinfo/extend<http://lists.ninenines.eu:81/listinfo/extend>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130117/19bfde40/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000039.html b/archives/extend/2013-January/000039.html new file mode 100644 index 00000000..adf15655 --- /dev/null +++ b/archives/extend/2013-January/000039.html @@ -0,0 +1,90 @@ + + + + [99s-extend] Cowboy feedback needed + + + + + + + + + + +

[99s-extend] Cowboy feedback needed

+ Loïc Hoguin + essen at ninenines.eu +
+ Thu Jan 24 22:23:31 CET 2013 +

+
+ +
Hey,
+
+I'm looking into perhaps starting a project related to Cowboy and could 
+use some feedback from users, particularly in the realm of numbers.
+
+If you use Cowboy and have it in production where:
+
+  *  Latency is vital
+  *  Throughput is vital
+  *  Concurrent number of connections is huge
+  *  Load is huge (or would be with another solution)
+
+Then I'd like to hear from you!
+
+Please send me average numbers, statistics, graphs or anything where I 
+can see how well it performs for you! In private if you prefer. Tell me 
+if I can quote you or your company about it. Please answer even if we 
+briefly discussed it in the past.
+
+(If you found that it didn't perform enough for your needs you should 
+probably open a ticket, or, if you can't, send me a private email.)
+
+Looking forward to the feedback. Thanks!
+
+-- 
+Loïc Hoguin
+Erlang Cowboy
+Nine Nines
+http://ninenines.eu
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000040.html b/archives/extend/2013-January/000040.html new file mode 100644 index 00000000..81f5ad61 --- /dev/null +++ b/archives/extend/2013-January/000040.html @@ -0,0 +1,77 @@ + + + + [99s-extend] Cowboy Makefile + + + + + + + + + + +

[99s-extend] Cowboy Makefile

+ Grzegorz Junka + list1 at gjunka.com +
+ Thu Jan 24 23:41:30 CET 2013 +

+
+ +
Hi,
+I understand the move away from Rebar but I'd like to see the project to 
+be still Rebar-compatible. Would that be a problem? Mainly I am thinking 
+about dependencies. The Cowboy Makefile assumes that Ranch is in its 
+deps folder. If Cowboy is a part of a bigger application, and most often 
+it will be in such a role rather than a standalone application, then all 
+dependencies should be kept in one place. In that case it would be the 
+main project's deps folder, not Cowboy's deps folder. Can the 
+compilation process be split into compiling Cowboy dependencies 
+separately from Cowboy itself?
+
+something like:
+
+all: compile-deps compile-cowboy
+
+Then if Cowboy is a dependency itself it may be just compiled without 
+the dependency (as it will be compiled when the main project is compiled).
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000041.html b/archives/extend/2013-January/000041.html new file mode 100644 index 00000000..33df9c64 --- /dev/null +++ b/archives/extend/2013-January/000041.html @@ -0,0 +1,112 @@ + + + + [99s-extend] [erlang-questions] Cowboy feedback needed + + + + + + + + + + +

[99s-extend] [erlang-questions] Cowboy feedback needed

+ Barco You + barcojie at gmail.com +
+ Fri Jan 25 06:53:17 CET 2013 +

+
+ +
Hi Loic,
+
+I'd like to send feedback very much. But right now Cowboy is just used as
+demo in my company --- BesTV (www.bestv.com.cn), which is the largest IPTV
+and intenetTV operator in China. Although I think Cowby is good, the
+production environment is still dominated by Java and mainstream HTTP
+servers. Because I'm from Ericsson, I hope to promote Erlang here but it's
+not so easy. I would send the data if Cowboy would be used in production
+and fully tested.
+
+Thank you!
+Barco
+
+On Fri, Jan 25, 2013 at 5:23 AM, Loïc Hoguin <essen at ninenines.eu> wrote:
+
+> Hey,
+>
+> I'm looking into perhaps starting a project related to Cowboy and could
+> use some feedback from users, particularly in the realm of numbers.
+>
+> If you use Cowboy and have it in production where:
+>
+>  *  Latency is vital
+>  *  Throughput is vital
+>  *  Concurrent number of connections is huge
+>  *  Load is huge (or would be with another solution)
+>
+> Then I'd like to hear from you!
+>
+> Please send me average numbers, statistics, graphs or anything where I can
+> see how well it performs for you! In private if you prefer. Tell me if I
+> can quote you or your company about it. Please answer even if we briefly
+> discussed it in the past.
+>
+> (If you found that it didn't perform enough for your needs you should
+> probably open a ticket, or, if you can't, send me a private email.)
+>
+> Looking forward to the feedback. Thanks!
+>
+> --
+> Loïc Hoguin
+> Erlang Cowboy
+> Nine Nines
+> http://ninenines.eu
+> ______________________________**_________________
+> erlang-questions mailing list
+> erlang-questions at erlang.org
+> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: <http://lists.ninenines.eu/archives/extend/attachments/20130125/7d0820aa/attachment.html>
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/000042.html b/archives/extend/2013-January/000042.html new file mode 100644 index 00000000..c3394073 --- /dev/null +++ b/archives/extend/2013-January/000042.html @@ -0,0 +1,92 @@ + + + + [99s-extend] [erlang-questions] Cowboy feedback needed + + + + + + + + + + +

[99s-extend] [erlang-questions] Cowboy feedback needed

+ Michael Truog + mjtruog at gmail.com +
+ Fri Jan 25 07:26:27 CET 2013 +

+
+ +
A comparison (summary) of cowboy 0.6.1 and misultin 0.9 final in the context of CloudI is here:
+https://github.com/okeuday/CloudI/blob/master/src/tests/http_req/loadtest/results_v1_1_0/201210_summary.pdf
+(the raw Tsung results are also within the same directory)
+
+The results are just showing the latency when putting cowboy and misultin under 10kreq/s load with both 20k and 40k connections, when the requests go through CloudI messaging into all the supported programming languages (Erlang, C/C++, pure-Java, Python/C, pure-Python, and pure-Ruby.... the "pure" part is where only the target language is used to create the CloudI API, which does the Erlang binary term format CloudI request encoding/decoding).  So, the test is showing the performance of a simple HTTP GET query parameter parse/response using XML (the XML is based on historical misultin testing).
+
+For these tests, it showed cowboy always has less latency which is significant, if the programming language internal latency is not significant.  The cpu usage of cowboy was slightly lower than misultin for high connection counts (40k instead of 20k).  The memory usage of cowboy was significantly lower than misultin.  The test results are for R15B01 and R15B02, just due to when I did the loadtesting.
+
+I will continue to do similar loadtests in the future to make sure and evaluate performance with more recent Erlang releases, as time allows, but the Tsung configurations are within the repository for people to test their own (hardware) environments.
+
+On 01/24/2013 01:23 PM, Loïc Hoguin wrote:
+> Hey,
+>
+> I'm looking into perhaps starting a project related to Cowboy and could use some feedback from users, particularly in the realm of numbers.
+>
+> If you use Cowboy and have it in production where:
+>
+>  *  Latency is vital
+>  *  Throughput is vital
+>  *  Concurrent number of connections is huge
+>  *  Load is huge (or would be with another solution)
+>
+> Then I'd like to hear from you!
+>
+> Please send me average numbers, statistics, graphs or anything where I can see how well it performs for you! In private if you prefer. Tell me if I can quote you or your company about it. Please answer even if we briefly discussed it in the past.
+>
+> (If you found that it didn't perform enough for your needs you should probably open a ticket, or, if you can't, send me a private email.)
+>
+> Looking forward to the feedback. Thanks!
+>
+
+
+
+ + +
+

+ +
+More information about the Extend +mailing list
+ diff --git a/archives/extend/2013-January/author.html b/archives/extend/2013-January/author.html new file mode 100644 index 00000000..abc837cb --- /dev/null +++ b/archives/extend/2013-January/author.html @@ -0,0 +1,122 @@ + + + + The Extend January 2013 Archive by author + + + + + +

January 2013 Archives by author

+ +

Starting: Thu Jan 3 10:30:30 CET 2013
+ Ending: Fri Jan 25 07:26:27 CET 2013
+ Messages: 15

+

+

+ Last message date: + Fri Jan 25 07:26:27 CET 2013
+ Archived on: Wed May 28 18:41:42 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-January/date.html b/archives/extend/2013-January/date.html new file mode 100644 index 00000000..451345ad --- /dev/null +++ b/archives/extend/2013-January/date.html @@ -0,0 +1,122 @@ + + + + The Extend January 2013 Archive by date + + + + + +

January 2013 Archives by date

+ +

Starting: Thu Jan 3 10:30:30 CET 2013
+ Ending: Fri Jan 25 07:26:27 CET 2013
+ Messages: 15

+

+

+ Last message date: + Fri Jan 25 07:26:27 CET 2013
+ Archived on: Wed May 28 18:41:42 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-January/index.html b/archives/extend/2013-January/index.html new file mode 100644 index 00000000..262a0ac7 --- /dev/null +++ b/archives/extend/2013-January/index.html @@ -0,0 +1,151 @@ + + + + The Extend January 2013 Archive by thread + + + + + +

January 2013 Archives by thread

+ +

Starting: Thu Jan 3 10:30:30 CET 2013
+ Ending: Fri Jan 25 07:26:27 CET 2013
+ Messages: 15

+

+

+ Last message date: + Fri Jan 25 07:26:27 CET 2013
+ Archived on: Wed May 28 18:41:42 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-January/subject.html b/archives/extend/2013-January/subject.html new file mode 100644 index 00000000..6bf3ddc3 --- /dev/null +++ b/archives/extend/2013-January/subject.html @@ -0,0 +1,122 @@ + + + + The Extend January 2013 Archive by subject + + + + + +

January 2013 Archives by subject

+ +

Starting: Thu Jan 3 10:30:30 CET 2013
+ Ending: Fri Jan 25 07:26:27 CET 2013
+ Messages: 15

+

+

+ Last message date: + Fri Jan 25 07:26:27 CET 2013
+ Archived on: Wed May 28 18:41:42 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/archives/extend/2013-January/thread.html b/archives/extend/2013-January/thread.html new file mode 100644 index 00000000..262a0ac7 --- /dev/null +++ b/archives/extend/2013-January/thread.html @@ -0,0 +1,151 @@ + + + + The Extend January 2013 Archive by thread + + + + + +

January 2013 Archives by thread

+ +

Starting: Thu Jan 3 10:30:30 CET 2013
+ Ending: Fri Jan 25 07:26:27 CET 2013
+ Messages: 15

+

+

+ Last message date: + Fri Jan 25 07:26:27 CET 2013
+ Archived on: Wed May 28 18:41:42 CEST 2014 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.3