[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#619347: Jappix - clarification



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Daniel,


> Thanks for your efforts to make a package of Jappix, I am also 
> interested in trying it

The source and binary packages are available now on the Debian Mentors
page [0]. Even if they are not yet in the Debian archives, I try to
keep those packages up to date.

> I recently evaluated Candy, I notice it can only really do MUC
> chat rooms and it had problems with doing private chats.  Is the
> Jappix client known to be stable for both types of chat?

I run a test instance on https://jabber.deuxpi.ca/ that runs over
Prosody. It seems to work well enough for me. In the past, that same
server was running ejabberd and I remember it had major limitations.

> One thing that is not clear from the description: does it provide
> any server-side capabilities?  I notice a lot of PHP code, I
> haven't looked inside that, but is it doing any of the XMPP
> server-side functionality in that code?  Can the JavaScript chat
> client be used standalone without the PHP code, e.g. JavaScript
> just talking to the BOSH server (e.g. ejabberd)?

You are right. Jappix does not provide any server-side capabilities.
The JavaScript client is JSJac, which is also used by JWChat. If you
are looking for a simpler web client, you could look at that program
instead.

> Based on the above question, is it possible that the package could
> be split into multiple packages, e.g. one package for the
> JavaScript client and another package with the PHP stuff just for
> those people who want that?

This is a question that should be asked to the Jappix developer
themselves. I know they have a "mini" mode already so that the Jappix
code can be embedded into larger web apps.


[0] https://mentors.debian.net/package/jappix


Regards,


Philippe Gauthier <philippe.gauthier@deuxpi.ca>
http://www.deuxpi.ca/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlHlZ2UACgkQdX62PscofCSO+wCgk+1Kr+bcI4MflYPjvsfn15gO
eVsAn0qwC6VRGBvdFrluHn7Ztqfp7Mfj
=0OEy
-----END PGP SIGNATURE-----


Reply to: