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? 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
