El Martes, 17 de Febrero de 2009, Dale Worley escribió: > On Mon, 2009-02-16 at 22:28 +0100, Iñaki Baz Castillo wrote:
> This is yet another place in the BNF where what needs to be done is > determined by the parameter name. This case is more complex than usual, > in that the parameter name determines whether it is an accept-param (and > binds to media-range as part of accept-range), or an m-parameter (and > binds to "m-type SLASH m-subtype" as part of media-range. The problem is that both 'accept-param' and 'm-parameter' accept any custom parameter (token EQUAL token). > And as you know, no ordinary parser can solve this. My choice of > implementation would be to eliminate accept-param in the parser, so all > trailing parameters are part of the media-range, and then have a > post-processor move the correct parameters from there to accept-range. Yes, this is exactly what I've done :) Thanks a lot. -- Iñaki Baz Castillo _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
