Bogdan-Andrei Iancu wrote:
Federico Giannici wrote:
So you are saying that if it happens that two separate and independent modules for a pure chance modify the same header field, the resulting message is corrupt???
yes.
I think this is a GREAT limitation (I'd call it a bug) of the lumps handling code...
it's not a limitation of the code, but of the concept. having a set of parallel changes starting from the same initial text may lead to inconsistency..... that's a tribute for speed.....
I remain convinced that, if parallel modifications of different HFs is possible (so there must be a mechanism to update pointers to others HFs), then two modifications of the same HF should be possible too.
Unfortunately, I'm not a good enough C programmer to do it... ;-)
Bye.