Vieri could you please describe a little more the use case from the
functionality that you have mention?
Which functionality? The one I posted on JIRA (1)? Or the yet-to-be-implemented JSON/HTTP "contact source" (2)?
1- With this hack Jitsi only has a new icon right next to the "search field". If I press that button, the default browser is opened and directed to a URL with whatever parameters Jitsi can pass with either GET or POST (username, ip addr, etc. and of course the search string). So I can program the contact searching logic on the web server and display it as I wish (any format I like - images, tables, etc). The links within the contact web page I generate can interact with Jitsi if I use eg. sip: or xmpp: to make calls or open chat conversations. It's really a simple hack and quite useful and flexible. On the other hand it's not integrated in Jitsi so it's not that elegant.
2- With this other solution, you'd have another "contact source" just like all the others already available but based on HTTP/HTTPS. That makes the output of the contact list more flexible to program from an admin's point of view and you can set it up on a rmeote server since HTTP is better for that than, say, LDAP/AD. The advantages of (2) over (1) is that the contact list is "integrated" within Jitsi and you can perform several actions on a given contact (not just call it but also save it to the "buddy list", etc.).
Just giving out ideas...
--- On Thu, 1/24/13, a.bourazanis <firstname.lastname@example.org> wrote: