[Sip-implementors] SIP Lazier Parser
feng.w.qin at gmail.com
Tue Sep 20 00:43:52 EDT 2005
Sorry, requirement doesn't mean the requirement in "RFC"
On 9/19/05, Nataraju A B <bnataraju at kodiaknetworks.com> wrote:
> RFC 33261 does nto specify how to parse it ??
> It does only specify only what should be the grammar to be conformant
> I think if you use lex and yacc for this parsing operation u can
> optimize depending on various speed and memory variations.. - BUT THIS
> is no where mentioned in RFC as a requirement/constraint...
> Thanks & Regards,
> Nataraju A.B.
> -----Original Message-----
> From: sip-implementors-bounces at cs.columbia.edu
> [mailto:sip-implementors-bounces at cs.columbia.edu] On Behalf Of Feng QIN
> Sent: Saturday, September 17, 2005 10:10 PM
> To: sip-implementors at cs.columbia.edu
> Subject: [Sip-implementors] SIP Lazier Parser
> Hello all,
> Do you ever meet such requirement?
> - In parser, we don't want to parse the whole sip message at one time,
> parse the part we want, e.g.if we only need request-uri, the req-uri
> will only be done when we call "osip_message_get_requri"...
> I think this requirement will make the some specific application (SIP
> Distributor) more faster (Only care the message part we want to care).
> How do you think about it?
> Je suis souvent très occupé.
> QIN Feng
> Sip-implementors mailing list
> Sip-implementors at cs.columbia.edu
Je suis souvent très occupé.
More information about the Sip-implementors