Would be these system reimplemented in Erlang or other languages if they have dropped ejabberd?
<br><br>What's the status of <a href="http://jabber.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Jabber.org</a>?<br><br>Is this string-binary problem a language problem or ejabberd implementation issue?
<br><br>BR!<br>james<br><br><div><span class="gmail_quote">2006/8/30, Joel Reymont <<a href="mailto:email@example.com">firstname.lastname@example.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>On Aug 29, 2006, at 4:59 PM, Dmitrii Dimandt wrote:<br><br>> And there are both advantages and disadvantages to that, as there<br>> always<br>> are, but I think, that if Erlang community could focus on the<br>
> disadvantages... Man, this could be the next killer-language :)<br>> (Ruby is<br>> slowly filling the void, and C# 3.0 is around the corner, and there<br>> is that<br>> curious little fellow by the name of Nemerle...)
<br><br>Why not Ruby on the Erlang VM?<br><br>Even the "flagship" Erlang apps have their problems. ejabberd uses<br>tons of memory because strings are being passed around as lists<br>despite being received as binaries from the socket. This is a problem
<br>on 32-bit systems as it limits the number of users you can host and<br>it's a bigger problem on 64-bit systems as words are LARGER.<br><br>The ejabberd developers came up with a fix, they are loading expat (C<br>parser) as a driver. They are still using a port per message or per
<br>connection (don't remember exactly) and blow through the number of<br>ports normally configured. Yes, you can up the number of ports but a<br>better solution would be to stop using strings and create a shared<br>pool of XML parser ports.
<br><br>Some high-profile messaging startups are using ejabberd now, although<br>they don't advertise it. They are also considering dropping ejabberd<br>and either going with a commercial implementation or writing their<br>
own stuff. I know because I keep in touch with them.<br><br>Despite the Ericsson AXD 301 advocacy there are no high-profile<br>Erlang deployments that I know about. There should be and we should<br>all know! That is if we want Erlang to become mainstream. On the
<br>other hand, why bother?<br><br>--<br><a href="http://wagerlabs.com/">http://wagerlabs.com/</a><br><br><br><br></blockquote></div><br>