Re: Add supervisor:start_child/3 to limit the number of children
Siri Hansen <[email protected]> Fri, 16 Jan 2015 14:15:09 +0100
| Newsgroups | gmane.comp.lang.erlang.patches |
|---|---|
| Message-ID | <CAGqERUEOUnd9v_w54Ko8c3Lhgw_UgWMTgWfFNv2M9qOWWBZK0Q@mail.gmail.com> |
--===============5545385221708545786== Content-Type: multipart/alternative; boundary=047d7b33d42e10b312050cc4c3b9 --047d7b33d42e10b312050cc4c3b9 Content-Type: text/plain; charset=UTF-8 2015-01-16 12:17 GMT+01:00 Vance Shipley <[email protected]>: > On Thu, Jan 15, 2015 at 8:30 PM, Siri Hansen <[email protected]> wrote: > > I'm happy to announce that in OTP-18, the supervisor API will be > improved to allow supervisor flags and childspecs declared as maps (similar > to http://erlang.org/pipermail/erlang-patches/2012-January/002574.html, > except maps are used instead of proplists). This will allow for additions > to these data structures. We now wonder if the functionality handled in the > current thread is still wanted, and if so if the patch should be rewritten > to use the new API? > > Yes, indeed it is. I will submit a new patch. > Great! As you know we need to be extra careful when including new functionality in the OTP base, so we might need to go another round with OTP Technical Board. So to avoid wasting time it might be a good idea to give us a short description of the design (including API) before implementing the details and we will give you feedback as soon as possible. /siri --047d7b33d42e10b312050cc4c3b9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo= te">2015-01-16 12:17 GMT+01:00 Vance Shipley <span dir=3D"ltr"><<a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>>= </span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Thu, Jan 15,= 2015 at 8:30 PM, Siri Hansen <<a href=3D"mailto:[email protected]">e= [email protected]</a>> wrote:<br> > I'm happy to announce that in OTP-18, the supervisor API will be i= mproved to allow supervisor flags and childspecs declared as maps (similar = to <a href=3D"http://erlang.org/pipermail/erlang-patches/2012-January/00257= 4.html" target=3D"_blank">http://erlang.org/pipermail/erlang-patches/2012-J= anuary/002574.html</a>, except maps are used instead of proplists). This wi= ll allow for additions to these data structures. We now wonder if the funct= ionality handled in the current thread is still wanted, and if so if the pa= tch should be rewritten to use the new API?<br> <br> </span>Yes, indeed it is.=C2=A0 I will submit a new patch.<br></blockquote>= <div><br></div><div>Great! As you know we need to be extra careful when inc= luding new functionality in the OTP base, so we might need to go another ro= und with OTP Technical Board. So to avoid wasting time it might be a good i= dea to give us a short description of the design (including API) before imp= lementing the details and we will give you feedback as soon as possible.</d= iv><div><br></div><div>/siri</div></div></div></div> --047d7b33d42e10b312050cc4c3b9-- --===============5545385221708545786== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ erlang-patches mailing list [email protected] http://erlang.org/mailman/listinfo/erlang-patches --===============5545385221708545786==--