Re: [reSIProcate-users] how to convert MsgHeaderScannerFSM to digraph?

[Byron Campen <bcampen@xxxxxxxxxxxx>]

Ok, I see what is happening here. With single-value headers, we ignore commas entirely. So, To: sip:bob@foo, sip:joe@foo would parse the value as "sip:bob@foo, sip:joe@foo". Additionally, this is how we manage to support extension headers that have commas in them, like the following from RFC 4475:

UnknownHeaderWithUnusualValue: ;;,,;;,;

Unknown headers are treated as single value by the pre-parser to avoid mistakenly tokenizing with commas.

Best regards,

Byron Campen

Hi Adam,

 How is State 7:ScanWhitespaceAfterNFieldName reached?
Under what condition are NValue and NFieldName  used?

The graph is attached.

Thanks


Frank

On Thu, Apr 23, 2009 at 11:22 AM, fuliang yuan <fuliangyuan@xxxxxxxxx> wrote:

Hi Adam,

It works fine with GVedit.

Thanks a lot!

Frank

On Thu, Apr 23, 2009 at 10:32 AM, Adam Roach <adam@xxxxxxxxxxx> wrote:

fuliang yuan wrote:

Hi,

I dumped MsgHeaderScanner FSM, but have no idea what tool should be used to convert it to diagraph.
Any help is appreciated.
 

You use the "dot" tool, which is part of the "graphviz" software suite. Your OS distribution probably has a package for it (using, for example, apt-get, yum, ports, or the Cygwin installer) -- or you can download it here:

http://www.graphviz.org/

/a

<FSM>_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature