What I would do is remove ns_conn encoding or make it read-only. It is not really necessary as it can be replaced by ns_startcontent or ns_adp_mimetype and is (largely) ignored by ns_return. And it confuses programmers (like me).
The problem is: backwards compatibility. Sry ... I forgot a possible use: When you want to change the encoding while sending streamed content (adp-file or ns_write), you have to use ns_conn encoding. So if it is not possible (or sensible) to remove the function, i would be grateful if there was a hint in the (future) documentation, that one should be VERY careful with the use of ns_conn encoding and that ns_return is completely independant of anything you set with ns_conn encoding (if there's a default OutputCharset).
