[jdev] Re: Re: The State of Our Code-bases

[Trejkaz Xaoza]

On Fri, 3 Sep 2004 07:04, you wrote:
> I guess it is possible to start multiple ejabberd instances on one
> machine. Different ports, of course, but this is not problem as SRV
> record should be used to find the right port. So the
> virtual-hosts-problem is solveable.

True.  I just have to wait until all of our 1000+ users switch to a client 
which supports SRV.  I haven't even done so myself yet. :-)

> > That there is still so much criticism directed at Jabberd for its
> > difficulty to get working, reflects not only on Jabberd itself, but on
> > the people who created packages for their distros, which were supposed to
> > work out of the box.
>
> Which jabberd do you mean. Jabberd 1.4.x is not XMPP compliant and XMPP
> is supposed to be the current Jabber protocol. Jabberd 2.0 is buggy --
> unstable and probably insecure (most crashes are because of buffer
> overflows and similar problems). It is not ready for proffesional use.

Actually, I was just speaking generically.  Our server can't run Jabberd2 yet 
as there seems to be some user which is able to crash the server in an 
instant.  On the other hand, maybe one day someone will craft a c2s module 
for 1.4 which can do XMPP...

TX

-- 
'Every sufficiently advanced technology is indistinguishable from magic' - 
Arthur C Clarke
'Every sufficiently advanced magic is indistinguishable from technology' - Tom 
Graves

             Email: Trejkaz Xaoza <trejkaz at xaoza.net>
          Web site: http://xaoza.net/trejkaz/
         Jabber ID: trejkaz at jabber.xaoza.net
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20040903/8af4b027/attachment-0002.pgp>