Christer Holmberg (JO/LMF) wrote: > And, I doubt anyone would use INFO for a real-time chat type of > applications, with lots of relatively small messages, since it would > overload intermediates.
Well, personally, I might. I think that MESSAGE could well have been an INFO usage. Instead, we developed a protocol extension that confused what was happening at the SIP level (transport) with an application function (Presenting data to the user). It was bad design. Once all the proxies that don't have to be there for something like NAT traversal have dropped out, the only intermediaries being loaded are the ones that need to be loaded in order to make the communication work at all. When one brings in the performance gains of SIPSEC (proxies no longer parse, decrypt, or encrypt messages once a CONNECT completes), it's actually a pretty efficient approach. -- Dean _______________________________________________ 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
