stream + content-length + chunking

Hi Chris --

 

 

Stream profile is low-overhead, performing replacements on the fly mid-stream, but requires chunking because the resulting payload size cannot be known when the Content-Length header would be sent.

 

 

Collecting the entire payload to perform replacement so size may be calculated is high overhead but allows explicit Content-Length declaration in header.

 

 

You can certainly use regsub to manipulate the entire payload, but as you suspected, it will carry a considerable performance hit. Search the forum & codeshare for "regsub" + "::payload" and you'll find a number of relevant examples.

 

 

/deb