From: Zoran V. <zv...@ar...> - 2006-08-14 14:48:44
|
On 08.08.2006, at 11:40, Michael Lex wrote: > For me it looks like the use cases for ns_conn encoding are rare, e.g. > if you use it in a context where the client knows exactly what > encoding to > expect. The documentation should mention the above alternatives and > warn not > to use ns_conn encoding if you "don't know all side effects." Lets put it this way: if you were to write all that from scratch, what would you do? Or, if you were allowed to revamp that (existing) interface(s) what would you remove/add? To be honest, we always serve utf-8 and never had any need to change the encodings, hence I (up to today) largely avoided to look at that code... But I see it deserves some cleanup. Cheers Zoran |