Hi Pedro,
Thanks for your quick reply :-)
On Thu, Jun 05, 2008 at 03:14:58PM +0100, Pedro Melo wrote:
> Hi,
>
> There is no std protocol to access the roster from an external
> component. I believe jabberd2 had some extensions to do it, but I
> might be wrong on that.
Aha. I guess I
On 06/05/2008 9:08 AM, Tomasz Sterna wrote:
> Dnia 2008-06-05, czw o godzinie 15:14 +0100, Pedro Melo pisze:
>> There is no std protocol to access the roster from an external
>> component. I believe jabberd2 had some extensions to do it, but I
>> might be wrong on that.
>
> I was thinking abou
Dnia 2008-06-05, czw o godzinie 15:14 +0100, Pedro Melo pisze:
> There is no std protocol to access the roster from an external
> component. I believe jabberd2 had some extensions to do it, but I
> might be wrong on that.
I was thinking about implementing in in jabberd2, but never got to it,
b
Hi,
On Jun 4, 2008, at 11:11 PM, Esteban Manchado Velázquez wrote:
> Hi,
>
> I would like to do something that I thought it would be very
> simple, but I
> can't figure out how to do it: I want access to user rosters from a
> component.
> The idea is customising the response to user reque
Hi,
I would like to do something that I thought it would be very simple, but I
can't figure out how to do it: I want access to user rosters from a component.
The idea is customising the response to user requests depending (e.g. service
discovery) on the contents of that user's roster.
I h
