[ragel-users] Re: ragel edge side include parser

[Paul Findlay]

> Putting the .* ahead of esi_tags is very costly. It grows the number of
> states from 80 to over 300. You can improve this by choosing some point
> at which to commit to esi_tags. But first we need to know more about the
> language. Is "<" on it's own legal? What is the nature of the "water" in
> which your esi_tag "island" is found?
The esi tags get embedded in HTML and other text formats right? Would
it be possible to keep track of the start of pure html (or whatever)
content, and if '<esi:' is hit, output all the content (if any) up to
'<esi:, unless the content occurs in some nested esi construct'?

 - Paul