You have to make users of the rich internet client appear of users of
the component. This is the easiest way - make the xmpp users have
xmpp server jid, and make the rich internet client users have a
different server jid.
You wouldn't be able to overlay both the main xmpp domain, and the
Op woensdag 14 september 2005 05:50, schreef Raffaele Sena:
Hello,
I am struggling with a problem and I thought of asking your opinion.
I want to use a Jabber/XMPP server for an enterprise application but I want
a much stricter integration that simply hosting an IM server on the same
On 14/09/05, Raffaele Sena [EMAIL PROTECTED] wrote:
What I would really like to do is have a single connection between the
application server and the XMPP server and some state information in the
application server for the connected clients. I thought that I could use the
server-to-server
Sander Devrieze wrote:
Op woensdag 14 september 2005 05:50, schreef Raffaele Sena:
Hello,
I am struggling with a problem and I thought of asking your opinion.
I want to use a Jabber/XMPP server for an enterprise application but I want
a much stricter integration that simply hosting an IM
Thanks to everybody that answered the question.
I started looking at the component protocol but there are a couple of
things I don't understand.
It is clear to me that if I send messages from a client to the component
JID the component will get the message. But I didn't see anywhere in the
Raffaele,
First, I would firgure out the max number of concurrent users of your
application. If it's not more than a couple hundred, you should just use
Smack or JSO (one client per connection) and not worry about it further.
However, there are certainly cases where one connection per client in
