Re^2: Truncation of individual "Nodes to Consider"

> Hmm, stuff with HTML is not that easy to truncate cleanly. It's certainly possible, but the server might have to generate the appropriate end tags.

PM is using a selfmade configurable parser to

"validate" the HTML and
activate the markup and
deactivate potentially malicious elements.

IMHO it's not 100% correct and has loopholes.

A truncation mechanism would need to be added on top of this, which is unlikely.

Anyway folding away huge branches of the DOM might be far better and easier than truncating, but would still require a better parser.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^2: Truncation of individual "Nodes to Consider"

Replies are listed 'Best First'.
Re^3: Truncation of individual "Nodes to Consider" by kcott (Archbishop) on Dec 03, 2021 at 11:02 UTC
G'day Rolf, ++ (x3) Thanks for the effort you put in to investigate this. It's appreciated. Yes, 64kB is roughly the number I seem to remember seeing in documentation somewhere on this site; unfortunately, I can't locate this and don't remember the exact number. Also, I'm pretty certain I've never attempted to post anything that large. It looks like implementing this request would involve a massive amount of work and, as such, probably won't happen. That's fine: it's just a feature, not a bug fix, and the situation that I described only occurs rarely. — Ken	[reply]

Replies are listed 'Best First'.

Re^3: Truncation of individual "Nodes to Consider"
by kcott (Archbishop) on Dec 03, 2021 at 11:02 UTC

G'day Rolf,

++ (x3) Thanks for the effort you put in to investigate this. It's appreciated.

Yes, 64kB is roughly the number I seem to remember seeing in documentation somewhere on this site; unfortunately, I can't locate this and don't remember the exact number. Also, I'm pretty certain I've never attempted to post anything that large.

It looks like implementing this request would involve a massive amount of work and, as such, probably won't happen. That's fine: it's just a feature, not a bug fix, and the situation that I described only occurs rarely.

— Ken

[reply]