> I took a look at the code and as far as I understand, there is really no need to change the APIs to allow lazy copy of chains.
Sure - it would be possible to do this without changing the API at the code level - but the ** contract ** changes - which is really part of the API. Filter implementors would not be able to cache NextFilters any more: And if they did, things would break (and you were very worried before about changes which would make it easier for users to break things). So if they upgrade and don't recode their filters accordingly, they've got a problem. That's what I mean by "impact". Hopefully Trustin will get back to us with his comments on this feature - then I'll know whether its worth me spending the time to implement the lazy copy or not. Dave This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
