<div dir="ltr"><br>Hi Guillaume,<br><br>Thank you for your message.<br><br>Though it is an external application, but its intended to be run on server (Application has similarities with server implementation like it runs Apache)<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>A) If that's an external application, then you have to connect to the<br>
jabber server as any client/XO. You'll be able to see all the connected<br>
XO's that are in your jabber roster. Currently we are using an ugly hack<br>
called "shared roster" meaning you'll see all the connected XO's but we<br>
plan to drop it soon.<br>
A solution could be to use Gadget [1] but we currently don't have API to<br>
search for buddies based on their alias (that's probably something<br>
useful to have so we could consider to add one).<br>
Another solution would be for each buddies to subscribe to your<br>
application (as a Friend) if they are interested about receiving SMS<br>
messages but that's not very convenient IMHO.</blockquote><div><br>The idea of having the API to search for buddies based on their nicks and forwarding message to them seems good. One of the solution to forward message can be a XMPP message, though I am not sure how to implement this. Can you think of any alternatives?<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
B) A server plugin. You'll be able to use the server API (and so be able<br>
to know which buddies are connected, etc) but you'll be depend on a<br>
server implementation and your app will have to run on the same box as<br>
the server.</blockquote><div><br>Server API doesn't let us know about the nicks of current buddies that are connected. As Wad meant to say, Jabber IDs are available which are not human readable and they cannot be mapped to nicks at present. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
C) A XMPP component. That's generally how XMPP gateways work. People<br>
will have to explicitly subscribe to your component.</blockquote><div><br>I don't have idea of (C). However, it does not seem convenient as students have to subscribe here.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
If you choose A. then I strongly suggest you to use Telepathy (Gabble)<br>
as we already have a nice API you could use instead of dealing with XMPP<br>
directly.<br></blockquote></div><br><br><br>Thanks.<br><br>Best,<br>Ankur<br><br><br><br><br></div>