Re: [reSIProcate] Message Adornment
To be clear, I am OK with moving to a model where you adorn based on
onReadyToSend. I had no personal issue with the current behavior. My
understanding was that the current behavior is an side-effect of some
design choices, not a design choice in itself.
It would be useful to capture the real motivation for this change in the
mailing list record.
RjS
On Jun 3, 2005, at 3:08 PM, Derek MacDonald wrote:
Consensus from a conf. call inspired by an adornment related bug; Rjs
and
Rohan think most adornments should be transient.
--Derek
CONFIDENTIALITY NOTICE
This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the
addressee(s)
only and access by anyone else is unauthorized. If you are not an
addressee,
any disclosure, distribution, printing or copying of the contents of
this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please
inform
the sender immediately and then delete this email and any copies of it.
Thank you for your co-operation.
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of david Butcher
Sent: Friday, June 03, 2005 12:45 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] Message Adornment
Motivation?
david
Quoting Derek MacDonald <derek@xxxxxxxx>:
The makeFoo methods in DialogUsageManager currently return a
SipMessage
which can be used to adorn messages. This adornment will appear in
all
subseqeuent requests in the dialog. For example, a custom header
that
is
put on an invite returned from makeInviteSession will appear in any
re-invites.
This is going to change so that adornment will only affect that
message
and
not any subsequent requests. To put a header on every outgoing
request
in
an InviteSession use onReadyToSend from InviteSessionHandler.
Equivalent
callbacks will be added to other handlers.
--Derek
CONFIDENTIALITY NOTICE
This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the
addressee(s)
only and access by anyone else is unauthorized. If you are not an
addressee,
any disclosure, distribution, printing or copying of the contents of
this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please
inform
the sender immediately and then delete this email and any copies of
it.
Thank you for your co-operation.
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel