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)?
it also could be a flag/options parameter when calling handle_publish(),
e.g.:
handle_publish("$avp(s:option1)$avp(s:option2)");
options:
"a": overwrite existing presentity instead of generating a new etag
when etag is missing
"b": do not send 412 error but accept existing etag and behave as if
the etag was missing
"c": always overwrite all existing presentities
The options would violate the RFC but will be useful with certain
services (like MWI or simple publishers)
Then, in openser.cfg you can detect the MWI publish and set the
respective flag.
regards
klaus
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
