For example, putting a markup like [(poor text)] in "blog.header", then all the post under "blog.*" can only accept a certain kinds of markups (customizable) to be rendered to html, others will treat as pure text.
linly On 3月17日, 下午12時39分, Linly <[email protected]> wrote: > Hi Dan, > > I've an interesting test on a page containing 1000+ lines, pure text, > no markup. > > On my web server if I save the 1000+ lines page, it takes about 30+ > seconds to finish the process, from clicking the save button to the > page display again. > > But if I add the "<code></code>" markup surrounding the whole content, > amazing result happened. The page takes 15 seconds to do the same job. > > Further more, if I put the "/* */" markup surrounding the whole > content, the same process takes only 5 seconds. > > Every time, the diff was saved successfully. So I think, it seems > BoltWire is taking a lot of time to do the markup parsing, rendering, > and output. > > Should we consider that there are so many different type of page > content out there. If we use one process to treat all of them, the > result is every page will be treated by the most tight parsing. > > But if I have a certain kind of content, say, a dictionary, or a blog, > the markup in it is very limited. Is it possible to force the markup > engine only parse a certain kind of markups? So we can speed up the > render and display? > > Cheers, linly --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
