<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5Berlang-questions%5D%20%5BANN%5D%20Ranch%200.6.0%20Xmas%20Edition%0A%09Released&In-Reply-To=%3C50E58CF4.9080804%40ninenines.eu%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000030.html">
<LINK REL="Next" HREF="000032.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20%5Berlang-questions%5D%20%5BANN%5D%20Ranch%200.6.0%20Xmas%20Edition%0A%09Released&In-Reply-To=%3C50E58CF4.9080804%40ninenines.eu%3E"
TITLE="[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released">essen at ninenines.eu
</A><BR>
<I>Thu Jan 3 14:51:48 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="000030.html">[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released
</A></li>
<LI>Next message: <A HREF="000032.html">[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#31">[ date ]</a>
<a href="thread.html#31">[ thread ]</a>
<a href="subject.html#31">[ subject ]</a>
<a href="author.html#31">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>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> I mean situation that after cowboy:update_options existing acceptors are
</I>><i> still working with old routes.
</I>><i> Currently it is useless API, so I have to stop cowboy and start it back.
</I>><i>
</I>><i>
</I>><i> On Thu, Jan 3, 2013 at 4:46 PM, Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>
</I>><i> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>> wrote:
</I>><i>
</I>><i> Haven't had any stability issue. What we did here is ensure that
</I>><i> when any process gets killed for any reason, especially reasons we
</I>><i> can't foresee, Ranch continues to work as expected.
</I>><i>
</I>><i> Ranch not updating protocol options for existing connections isn't a
</I>><i> problem, it won't be "fixed". Ranch can't guess how connection
</I>><i> processes are implemented. It's up to you to allow this if you need
</I>><i> it. The upgrade updates the options for all acceptors and all future
</I>><i> connections, that's it.
</I>><i>
</I>><i>
</I>><i> On 01/03/2013 10:30 AM, Max Lapshin wrote:
</I>><i>
</I>><i> Loic, it would be great to hear a bit, what problems have you
</I>><i> met with.
</I>><i>
</I>><i> What issues with stability can be in acceptor pool?
</I>><i>
</I>><i> Also I have question about updating protocol options: have you done
</I>><i> something with the problem that after updating protocol options
</I>><i> existing
</I>><i> workers are running with old config?
</I>><i>
</I>><i> On Tuesday, December 25, 2012, Loïc Hoguin wrote:
</I>><i>
</I>><i> Ho ho ho!
</I>><i>
</I>><i> I have just tagged version 0.6.0 of the Ranch project!
</I>><i>
</I>><i> Ranch is a socket acceptor pool for TCP protocols.
</I>><i>
</I>><i> <A HREF="https://github.com/extend/____ranch">https://github.com/extend/____ranch</A>
</I>><i> <<A HREF="https://github.com/extend/__ranch">https://github.com/extend/__ranch</A>>
</I>><i> <<A HREF="https://github.com/extend/__ranch">https://github.com/extend/__ranch</A>
</I>><i> <<A HREF="https://github.com/extend/ranch">https://github.com/extend/ranch</A>>>
</I>><i>
</I>><i>
</I>><i> Ranch is used by the next version of Cowboy, 0.8.0, set to be
</I>><i> released early February, but also in Basho's Riak
</I>><i> multi-data center
</I>><i> replication amongst others.
</I>><i>
</I>><i> All tickets have been resolved. A significant contribution
</I>><i> was made
</I>><i> by Andrew Majorov to improve the fault tolerance
</I>><i> capabilities of the
</I>><i> application, making sure it always restarts properly when
</I>><i> things go
</I>><i> wrong. This has been made possible thanks to the amazing
</I>><i> project
</I>><i> from Daniel Luna, chaos_monkey
</I>><i> (<A HREF="https://github.com/dluna/____chaos_monkey">https://github.com/dluna/____chaos_monkey</A>
</I>><i> <<A HREF="https://github.com/dluna/__chaos_monkey">https://github.com/dluna/__chaos_monkey</A>>
</I>><i> <<A HREF="https://github.com/dluna/__chaos_monkey">https://github.com/dluna/__chaos_monkey</A>
</I>><i> <<A HREF="https://github.com/dluna/chaos_monkey">https://github.com/dluna/chaos_monkey</A>>>).
</I>><i>
</I>><i>
</I>><i> The guide has also been improved and completed.
</I>><i>
</I>><i> <A HREF="http://ninenines.eu/docs/en/____ranch/HEAD/guide/introduction">http://ninenines.eu/docs/en/____ranch/HEAD/guide/introduction</A>
</I>><i> <<A HREF="http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction">http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction</A>>
</I>><i>
</I>><i>
</I>><i> <<A HREF="http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction">http://ninenines.eu/docs/en/__ranch/HEAD/guide/introduction</A>
</I>><i> <<A HREF="http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction">http://ninenines.eu/docs/en/ranch/HEAD/guide/introduction</A>>>
</I>><i>
</I>><i> If the guide isn't enough, drop by our new IRC channel
</I>><i> dedicated to
</I>><i> Cowboy, Ranch and all our other projects! #ninenines on
</I>><i> Freenode.
</I>><i>
</I>><i> Following is the list of change since last time:
</I>><i>
</I>><i> * Improve fault tolerance thanks to chaos_monkey testing
</I>><i> * Add 'nodelay' option to transports
</I>><i> * Add 'verify' option to ranch_ssl transport
</I>><i> * Add 'socket' option to pass an already open socket to
</I>><i> the listener
</I>><i> * Add Transport:sendfile/2 function (uses a fallback if
</I>><i> unavailable)
</I>><i> * Allow IP tuples in Transport:connect/3
</I>><i> * Add ranch:set_max_connections/2 to update the value live
</I>><i> * Add ranch:get_max_connections/1 to retrieve it
</I>><i>
</I>><i> We are always looking for feedback, especially now that
</I>><i> there is no
</I>><i> ticket left open on this project. If you are using Ranch
</I>><i> and have
</I>><i> questions or needs that it doesn't cover, please send them
</I>><i> to us.
</I>><i>
</I>><i> Commercial support will be available starting from January,
</I>><i> ping me
</I>><i> if you are interested. Details will be announced at a later
</I>><i> time on
</I>><i> the ninenines.eu <<A HREF="http://ninenines.eu">http://ninenines.eu</A>>
</I>><i> <<A HREF="http://ninenines.eu">http://ninenines.eu</A>> mailing list.
</I>><i>
</I>><i>
</I>><i> I want to thank all contributors for helping this project
</I>><i> by opening
</I>><i> tickets, sending patches and offering feedback. I am as
</I>><i> always very
</I>><i> grateful for any and all contributions. I wouldn't have
</I>><i> made it this
</I>><i> far without the tremendous help I receive everyday.
</I>><i>
</I>><i> Thanks to all and have a nice holiday!
</I>><i>
</I>><i> --
</I>><i> Loïc Hoguin
</I>><i> Erlang Santa
</I>><i> Nine Nines
</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A>
</I>><i> ___________________________________________________
</I>><i> erlang-questions mailing list
</I>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">erlang-questions at erlang.org</A> <mailto:<A HREF="https://lists.ninenines.eu/listinfo/extend">erlang-questions at erlang.org</A>>
</I>><i> <A HREF="http://erlang.org/mailman/____listinfo/erlang-questions">http://erlang.org/mailman/____listinfo/erlang-questions</A>
</I>><i> <<A HREF="http://erlang.org/mailman/__listinfo/erlang-questions">http://erlang.org/mailman/__listinfo/erlang-questions</A>>
</I>><i> <<A HREF="http://erlang.org/mailman/__listinfo/erlang-questions">http://erlang.org/mailman/__listinfo/erlang-questions</A>
</I>><i> <<A HREF="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</A>>>
</I>><i>
</I>><i>
</I>><i>
</I>><i> --
</I>><i> Loïc Hoguin
</I>><i> Erlang Cowboy
</I>><i> Nine Nines
</I>><i> <A HREF="http://ninenines.eu">http://ninenines.eu</A>
</I>><i>
</I>><i>
</I>
--
Loïc Hoguin
Erlang Cowboy
Nine Nines
<A HREF="http://ninenines.eu">http://ninenines.eu</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000030.html">[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released
</A></li>
<LI>Next message: <A HREF="000032.html">[99s-extend] [erlang-questions] [ANN] Ranch 0.6.0 Xmas Edition Released
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#31">[ date ]</a>
<a href="thread.html#31">[ thread ]</a>
<a href="subject.html#31">[ subject ]</a>
<a href="author.html#31">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
