Is that behavior specific to the reference "jabberd" server (or it's xdb_file module), or is it part of the spec?
 
If one wanted to store the roster data in an LDAP directory, do any provisions need to be made to ensure that the subscribe='' and hidden=''  attributes are stored with roster items that have a subscription type of "none", but haven't been accepted or declined for a specific request?
 
Would it be better to simply create a new "subscription type" called "pending"?  I.E. if someone sends me a subscription request, they are added to my roster like this:
 
<item [EMAIL PROTECTED] subscription=pending>
 
Or is the use of the "subscribe" and "hidden" attributes part of the specification?
 
Thanks.
 
--sk!

>>> [EMAIL PROTECTED] 6/26/2002 3:20:02 PM >>>
On Wed, Jun 26, 2002 at 08:48:39PM +0000, Matthias Wimmer wrote:
> Hi!
>
> Is it correct, that I only get subscription requests as a user when I
> requested the roster before? It's no problem, just that I searched the
> whole day for the problem why I don't get the subscription requests in
> my script ;)

Yes, that's correct. The pending requests (while you're offline)
are stored in the roster in some hidden attributes. Sending an
IQ-get for iq:roster is the 'kick' that the JSM waits for before
sending you any pending requests.

dj
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to