[jdev] Anyone any recommendations for a production server? E.g. ejabberd, openfire., etc?

Tue Sep 16 16:11:54 UTC 2014

The mod_jinglenodes extension for ejabberd is out of date and requires some
fiddling to get it to work.

Also it is only needed for adding relay support, you don't need any server
extension to just make jingle calls peer 2 peer.

Cheers

Kirk
On 16 Sep 2014 13:18, "Steven Lloyd Watkin" <lloyd at evilprofessor.co.uk>
wrote:

> You are best getting info on scaling/load/etc from the prosody team
> themselves (see xmpp:prosody at conference.prosody.im).
>
> See also https://prosody.im/doc/jingle
>
> _____________________________________________________
>
> Steven Lloyd Watkin
> Software Engineer
> PHP ::: Java ::: Ruby ::: Node.js ::: XMPP
> lloyd at evilprofessor.co.uk (email+jid) ::: http://www.evilprofessor.co.uk
> Facebook / Twitter / Flickr: lloydwatkin
>
> Organiser of WORLD RECORD breaking charity event:
> Scuba Santas ::: http://www.scuba-santas.co.uk
> Supporting the RNLI & DDRC - 15th December 2013 - NDAC, Chepstow
>
> On 16 September 2014 12:31, Chris Fortmüller <chritsche at gmail.com> wrote:
>
>> Thanks to everyone for your suggestions. This mailing list is awesome!
>>
>> So far, I think ejabberd is definitely interesting as it has
>> mod_jinglenodes.
>>
>> Also Prosody seems to have a large fan base here! @Steven Lloyd Watkin:
>> What would you say is a safe upper limit for the number of clients one
>> Prosody instance can handle on ec2?
>>
>> Will also do some research into whether prosody has some kind of jingle
>> support
>>
>> Thanks to everyone!
>>
>> On Mon, Sep 15, 2014 at 12:20 PM, Kirk Bateman <kirk.bateman at gmail.com>
>> wrote:
>>
>>> Thanks,
>>>
>>> May look at prosody again for some simple build system notifications soon
>>>
>>> Cheers
>>>
>>> Kirk
>>>
>>> On 15 September 2014 11:17, Steven Lloyd Watkin <
>>> lloyd at evilprofessor.co.uk> wrote:
>>>
>>>> I believe Matt W and the team is working on clustering or at least
>>>> thinking about it.
>>>>
>>>> We don't have huge numbers on our server yet, but even though its a low
>>>> power ec2 instance prosody causes very little load.
>>>> On 15 Sep 2014 11:14, "Kirk Bateman" <kirk.bateman at gmail.com> wrote:
>>>>
>>>>> Lloyd,
>>>>>
>>>>> I trust your view so, any thoughts on scaling / clustering prosody ?
>>>>> easy ?
>>>>>
>>>>> Cheers
>>>>>
>>>>> Kirk
>>>>>
>>>>> On 15 September 2014 11:03, Steven Lloyd Watkin <
>>>>> lloyd at evilprofessor.co.uk> wrote:
>>>>>
>>>>>> Prosody all the way for low resource requirements and high levels of
>>>>>> awesome.
>>>>>> On 13 Sep 2014 01:13, "bear" <bear42 at gmail.com> wrote:
>>>>>>
>>>>>>> +1 to Prosody
>>>>>>>
>>>>>>> On Fri, Sep 12, 2014 at 8:11 PM, Steven Lloyd Watkin
>>>>>>> <lloyd at evilprofessor.co.uk> wrote:
>>>>>>> > Prosody, always :)
>>>>>>> >
>>>>>>> > On 13 Sep 2014 01:05, "Chris Fortmüller" <chritsche at gmail.com>
>>>>>>> wrote:
>>>>>>> >>
>>>>>>> >> Hi All,
>>>>>>> >>
>>>>>>> >> I am working on a little app that will have XMPP ability, and
>>>>>>> need a
>>>>>>> >> jabber server for this.
>>>>>>> >>
>>>>>>> >> I hope that user numbers will at least go into the ten thousands,
>>>>>>> maybe
>>>>>>> >> more.
>>>>>>> >>
>>>>>>> >> I am planning on hosting the server on the Amazon Web Services
>>>>>>> cloud.
>>>>>>> >>
>>>>>>> >> Does anyone favour any specific server implementations? I am
>>>>>>> currently
>>>>>>> >> looking at openfire and ejabberd, and would like to know what
>>>>>>> others think
>>>>>>> >> is a good choice and why. Of course, it would be nice to have a
>>>>>>> server that
>>>>>>> >> is easily clusterable/scalable, so as to handle a large amount of
>>>>>>> traffic as
>>>>>>> >> smoothly as posible
>>>>>>> >>
>>>>>>> >> I would also like for the server to support as many XEPs as
>>>>>>> possible.
>>>>>>> >>
>>>>>>> >> What would also be cool is if there is some support for Jingle,
>>>>>>> but I am
>>>>>>> >> not sure if any servers do this, since I am not sure if Jingle is
>>>>>>> part of
>>>>>>> >> XMPP/XEPs yet, and also, since I havent looked at the technical
>>>>>>> details of
>>>>>>> >> Jingle yet, I am not sure if the server needs to implement it at
>>>>>>> all, since
>>>>>>> >> it seems to be p2p.
>>>>>>> >>
>>>>>>> >> Would be happy to receive any and all input/suggestions/ideas!
>>>>>>> >>
>>>>>>> >> Thanks and best regards,
>>>>>>> >>
>>>>>>> >> Chris Fortmueller
>>>>>>> >>
>>>>>>> >> _______________________________________________
>>>>>>> >> JDev mailing list
>>>>>>> >> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>>>>> >> Unsubscribe: JDev-unsubscribe at jabber.org
>>>>>>> >> _______________________________________________
>>>>>>> >>
>>>>>>> >
>>>>>>> > _______________________________________________
>>>>>>> > JDev mailing list
>>>>>>> > Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>>>>> > Unsubscribe: JDev-unsubscribe at jabber.org
>>>>>>> > _______________________________________________
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Bear
>>>>>>>
>>>>>>> bear at xmpp.org (email)
>>>>>>> bear42 at gmail.com (xmpp, email)
>>>>>>> bear at code-bear.com (xmpp, email)
>>>>>>> http://code-bear.com/bearlog (weblog)
>>>>>>>
>>>>>>> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
>>>>>>> _______________________________________________
>>>>>>> JDev mailing list
>>>>>>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>>>>> Unsubscribe: JDev-unsubscribe at jabber.org
>>>>>>> _______________________________________________
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> JDev mailing list
>>>>>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>>>> Unsubscribe: JDev-unsubscribe at jabber.org
>>>>>> _______________________________________________
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> JDev mailing list
>>>>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>>> Unsubscribe: JDev-unsubscribe at jabber.org
>>>>> _______________________________________________
>>>>>
>>>>>
>>>> _______________________________________________
>>>> JDev mailing list
>>>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>>> Unsubscribe: JDev-unsubscribe at jabber.org
>>>> _______________________________________________
>>>>
>>>>
>>>
>>> _______________________________________________
>>> JDev mailing list
>>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>>> Unsubscribe: JDev-unsubscribe at jabber.org
>>> _______________________________________________
>>>
>>>
>>
>> _______________________________________________
>> JDev mailing list
>> Info: http://mail.jabber.org/mailman/listinfo/jdev
>> Unsubscribe: JDev-unsubscribe at jabber.org
>> _______________________________________________
>>
>>
>
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20140916/b50136fe/attachment.html>