[Devel] multiple presentity entries

[Anca-Maria Vamanu]

Since you use pua to send Publish requests you should not worry about 
this at all.
If you give a command without a etag parameter, the pua module should 
try to match a prevoius request with the same presentity uri and 
source_flag and send a Publish request with the stored entity-tag.
The information stored by pua survive after restart since they are 
periodically updated in database and restored upon restart.  Since you 
saw 2 Publish messages with different etags, it means that the record 
from pua table was somehow lost.
It might be because openser was force closed before the update period 
expired. You should set the pua module parameter - 'update_period' to a 
smaller value  to prevent this.


Anca

Juha Heinanen wrote:

>Anca-Maria Vamanu writes:
>
> > So generating a new entity-tag should be done for each initial Publish 
> > no matter if a record with the same attributes exist.
> > The idea is that there can be more publications for the same resource, 
> > useful in the case in which you have more devices registered with the 
> > same uri.
>
>in case of mwi, it does not make sense that there are two entries in
>presentity table for the same mailbox, for example:
>
>Messages-Waiting: yes
>
>and
>
>Messages-Waiting: no
>
>the one that arrived later should override the earlier one.  
>
>also without any bugs, it may happen that the mailbox has crashed or
>something and lost its ETag.  then it doesn't have any other chance than
>to send an initial publish request.
>
>would it be possible to have an event package specific parameter that
>tells what to do, i.e., should initial publish replace (update) possibly
>existing presentity entry or should it add a new one (default)?
>
>-- juha
>
>  
>