<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Sad news Roberto.<div><br><div>Anyway, thousands thanks for Misultin and hope you'll be still present to help the community (if needed).</div><div><br></div><div>Regards,</div><div><div>Zabrane</div><div><br></div><div><div>On Feb 16, 2012, at 4:56 PM, Roberto Ostinelli wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Dear list,</p><p>Misultin development has been discontinued.</p><p>There currently are three main webserver <em>libraries</em> which basically do similar things:</p>
<ul><li><a href="https://github.com/mochi/mochiweb">Mochiweb</a></li><li><a href="https://github.com/extend/cowboy">Cowboy</a></li><li><a href="https://github.com/ostinelli/misultin">Misultin</a></li></ul><p>Especially since the recent heavy development of Cowboy's HTTP
server, I believe there is way too much duplication of efforts going on
here. This is why Misultin's current 'state of the art' has been frozen
in the latest tag, <a href="https://github.com/ostinelli/misultin/tree/misultin-0.9">v0.9</a>,
to support all the companies currently using Misultin in their
production environment. I'm here to provide help, if needed, in moving
away from it. Thus, this server should be robust and stable enough to
continue serving your needs for some time.</p><p>Instead of letting this library stand on github without notice, and
getting developers still use this project, I have preferred to
explicitly state to gradually move away from it, so that efforts can be
concentrated around one server library only. It's hard enough to let one
'child' like this one go, but I believe it's best for the whole Erlang
community. There are many ways to try to help each other in the community, I believe this decision is now for the better.</p><p><strong>Mochiweb</strong> has been around the block for a while
and it's proven solid in production, I can only recommend it for all
basic webserver needs you might have.
<strong>Cowboy</strong> has a very interesting approach since it allows
to use multiple TCP and UDP protocols on top of a common acceptor pool.
It is a very modern approach, is very actively maintained and many
projects are starting to be built around it.</p><p>I'll personally concentrate my efforts around Cowboy, simply because the projects I'm involved in often require multiple procotols. I really hope that it'll live up to the expectations that I'm putting into this.<br>
</p><p>Thank you to everyone that has been supporting Misultin in these years. Hopefully its <strong>code usability</strong>,
which I still believe to be unmatched (well, I have developed it so how
could I feel differently about this ^^_), will provide inspiration for
some library interfaces.</p><p>Best to you all,</p><p>r.</p>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><div apple-content-edited="true"><br>
</div>
<br></div></div></body></html>