El Thursday 05 June 2008 18:49:00 Paul Kyzivat escribió: > > This is IMHO a **very** bad design of a protocol. Instead of using this > > ambiguous and difficult mechanims (for the parser) a simple solution > > could be avoid multivalues headers. > > Yes, it is. I guess you can blame the designers of http for this, or > maybe goes back to email.
And then, why not blame designers of SIP because cloning HTTP/SMTP protocol without making fix all their issues? ;) > It is certainly attractive to do a "light" parse into headers without > parsing the header content, and then only parse the details if needed. > And it can be done with care. If you want a general approach you could > process the abnf to generate a very simple grammar just for that > purpose. It will not be quite as simple as a fsm, because at least one > relevant rule (comment) is recursive. But it can be pretty simple. This is a great idea! I'll create a parser grammar just for spliting a multivalue header. Thanks a lot. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
