[reSIProcate] PUBLISH's ETag

[david Butcher]

It is permitted to change the etag but not required. It is up to the server.

david


On 9/22/05, Noiile <noiile at hotmail.com> wrote:
>
> Kenneth Ho, Hello
>  Maybe you are right, but how do you expain the examples in RFC3903
> section 15.
> It uses new entity-tag for each PUBLISH request(Publication?).
>  Noiile, noiile at hotmail.com
> 2005-9-23
>
> ----- Receiving the following content -----
> *Receiver:* Kenneth Ho <kenho at teltel.com>
> *Receiver:* noiile <noiile at hotmail.com>
> *Time:* 2005-09-21, 19:52:33
> *Subject:* Re: [reSIProcate] PUBLISH's ETag
>
>   It's the 2xx responses to initial PUBLISH requests that would have
> different entity-tags. Sequential PUBLISH requests and responses to the
> same document all have the same entity-tags as the one returned by 2xx
> response of the initial PUBLISH request. DUM's behavior is compilant to
> RFC3903, and since DUM generates entity-tags when needed, there is no
> need to have (and probably must not be) interface to user to modify
> entity-tags.
>
> Ken
>
> Noiile wrote:
> > Noiile, Hello
> >
> > I found that entity-tag can not be changed, because DUM use it to find
> > the corresponding ServerPublication. If ServerPublication use different
> > entity-tag in 2xx, dum will response 412 for next PUBLISH request.
> > But I can not understand, why the entity-tag can not be changed ?
> >
> > Code in DialogUsageManager::processPublish(const SipMessage& request)
> > if (request.exists(h_SIPIfMatch))
> > {
> > ServerPublications::iterator i =
> > mServerPublications.find(request.header(h_SIPIfMatch).value());
> > if (i != mServerPublications.end())
> > {
> > i->second->dispatch(request);
> > }
> > else
> > {
> > SipMessage response;
> > makeResponse(response, request, 412);
> > send(response);
> > }
> > }
> >
> > Noiile, noiile at hotmail.com <+noiile at hotmail.com> <mailto:
> noiile at hotmail.com <+noiile at hotmail.com>>
> > 2005-9-21
> >
> > ----- Receiving the following content -----
> > *Receiver:* Noiile <mailto:noiile at hotmail.com <+noiile at hotmail.com>>
> > *Receiver:* resiprocate-devel
> > <mailto:resiprocate-devel at list.sipfoundry.org<+resiprocate-devel at list.sipfoundry.org>
> >
> > *Time:* 2005-09-20, 17:43:33
> > *Subject:* [reSIProcate] PUBLISH's ETag
> >
> > resiprocate-devel, Hello
> >
> > According to RFC3903, the header entity-tag should different for
> > each PUBLISH request in the Publication, but dum send response for
> > PUBLISH use the same ETag, right?
> > Maybe it should be changed by Application, but the interface
> > ServerPublication::getEtag() return const, it confuse me.
> > and I think it should be implemented in DUM.
> >
> >
> > Noiile, noiile at hotmail.com <+noiile at hotmail.com> <mailto:
> noiile at hotmail.com <+noiile at hotmail.com>>
> > 2005-9-20
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel at list.sipfoundry.org<+resiprocate-devel at list.sipfoundry.org>
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050922/9b6f5954/attachment.htm>