El Miércoles, 9 de Diciembre de 2009, Dale Worley escribió: > On Tue, 2009-12-08 at 00:56 +0100, Iñaki Baz Castillo wrote: > > I just mean SIP/TEL URI's for two purposes: > > > > 1) For user/device SIP identity (I've never seen a SIP AoR containing > > parameters). > > > > 2) The XUI field of XCAP URI (XUI is the AoR of the user whose document > > we desire). > > > > So I could imagine no cases in whise these URI's have parameters (I > > hope). > > Let me repeat myself: > > "If your question is "Should my system be able to handle SIP URIs with > parameters?", the answer is "Yes.". Because if you don't, in the next > few months, some usage of your system will require it. It's a law of > nature. ;-)" > > It may be that in your application you can sensibly remove parameters > from such URIs, or allow a lookup to fail (because the URI is not in the > form that the database contains). But you do not want to have your > application fail in unexpected ways just because a URI contains a > parameter in a situation where you couldn't think of a reason for it to > have one.
Ok. I've allow URI parameters in the parser but I'll ignore then totally. Thanks. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
