[jdev] Re: Default privacy list not persistent

[Chris Chen]

Not showing an error might possibly be that Wildfire ignored the  
improperly formed request.  That I do not know.  But yes, what Magnus  
said is true.  The query listed below needs to be split up into 2  
queries.

Also, if I remember correctly, default list is stored on the server  
(supposed to).  A client must select a list to be an active list  
every time it logs in.  This active list only applies for that  
specific session and doesn't span across other sessions (multiple  
logins with different resources).  A default is selected if no active  
list is set.

Thanks,
Chris

On May 30, 2006, at 9:52 AM, Yves Goergen wrote:

> On 30.05.2006 16:47 (+0100), Magnus Henoch wrote:
>> Yves Goergen <nospam.list at unclassified.de> writes:
>>
>>> <iq type='set'>
>>>   <query xmlns='jabber:iq:privacy'>
>>>     <default name='my-blocks'/>
>>>     <active name='my-blocks'/>
>>>   </query>
>>> </iq>
>>
>> This stanza will cause a "bad request" error in ejabberd 1.0.0 and
>> 1.1.1.  Only one of <default/> and <active/> may be present.  To
>> perform both changes, you need to send two stanzas.
>
> Then why doesn't Wildfire return an error and shows my list as active
> and default afterwards?
>
> Cannot test the difference right now. Either MSN won't let me in after
> ages of thinking about it or the auth request doesn't arrive. (Also  
> with
> no active list.) Need to do that in a few days again.
>
> -- 
> Yves Goergen "LonelyPixel" <nospam.list at unclassified.de>
> http://beta.unclassified.de – My web laboratory.