Architcecture for winbindd client character conversion.

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jeremy Allison wrote:

>> It's not the nss plugin job to mess with locales.
> 
> Did you read my proposal ? Winbindd will mess with
> the character set conversion, nss will merely tell
> winbindd what character set the current client is
> using.

Just to mention a point, Jeremy's proposal assumes a
similar boundary for string conversion as we use for
incoming CIFS packets.  Instead of the wire being the
boundary, the incoming winbindd pipe request is the
boundary.

And while it may be a really bad idea for Unix to allow
per user locale settings, the fact is that it does.
All this discussion really just seems hinged on the
point that it is a bad idea to do this.  But we have fixed
so many issues where it was a bad idea in Unix/Windows,
what makes this one different?





cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG1HF2IR7qMdg1EfYRAkMXAJ4jjPGfdgXo7TYizUNcyNa7RwWVowCgqiJN
vjAa6SrboXXeMfUdtI3tyQo=
=a4ma
-----END PGP SIGNATURE-----