Hi,
>>> If the application on the receiving side (or the person your're
>>> talking to) has asked you to send a jpeg, it most likely knows what to do
>>> it.
>>> This is similar to when the receiver subscribes to an "jpeg event".
>>> The one sending the jpeg may not know what the receiver is going to do
>>> with it, but the one subscribing to the event knows.
>>
>> What if the receiving side has asked for jpegs foor two different
>> functionalities in the same dialog? How does it know which treatment
>> to apply to a given jpeg?
>>
>> The answer is: It looks at the event package wrapping the jpeg.
>> Without that function (which INFO doesn't currently have, and that
>> that's what is broken), it just doesn't know.
>
> INFO itself is not the problem - INFO simply carries the MIME. The problem,
> if there is one (depends on the use-case and what you are carrying), is that
> you don't provide enough information in the MIME (maybe Content-Disposition
> is not enough etc).
>
> NOTIFY doesn't solve this problem either - NOTIFY simply carries the event
> package. The what-to-do is defiend by the event package, or by some
> information within the event package.
>
> One question: do you think there should be a separate event for every
> possible way a receiver may process the jpeg?
>If there are different possible uses, and there is reason why the sender
>and the receiver need to agree on the use, then yes. If the different
>uses are strictly a matter of local preference, then no.
>
>In the case at hand, it may be that I just send you jpegs. If I happen
>to send one that is my picture, you will (perhaps) recognize it as me
>and decide to put it in your address book. And if I happen to send you a
>key map then maybe you will install it on your touch screen phone. If
>that is my only expectation, then fine.
>
>But if I expect that when I send you a jpeg of a key map that it will
>automatically be installed on your phone for the remaining duration of
>our call, then it is important that your device understand that.
I most likely will not allow you to install anything on my phone just like
that. We (or the applciations we are using) will most likely agree that you are
now going to send a key map, and then I will process it as such.
But, IF I allow you to install a kep map on my phone by default, at any time, I
agree that there must be some additional information, e.g in the MIME body.
Maybe a new Content-Disposition value, or something similar - or INFO event
packages. But, again, it's information associated with the data sent, and is
not related to core SIP.
But, in many cases you don't have the what-to-do problem. If you send ISUP, for
example. Or, if two applciations use INFO to exchange information using a
specific content-type. Or, when you send DTMF you do so because the other end
has asked you to do so for a specific purpose.
Regards,
Christer
Paul
> Regards,
>
> Christer
>
>
>
>
>
>
> _______________________________________________
> Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [EMAIL PROTECTED] for questions on current sip
> Use [EMAIL PROTECTED] for new developments on the application of sip
>
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
