> Existing programs depend on the ability to dynamically change the execution encoding (within reason) in order for a server process to concurrently serve multiple clients with different locale settings.

This seems like a very weird use case because it effectively limits server to processing requests on one thread, since as mentioned elsewhere in the document per-thread locale setting is still in the proposal phase. Do you have any examples? In my experience changing locale dynamically more often than not breaks programs' expectations.

On Tue, Oct 2, 2018 at 10:21 PM Tom Honermann <tom@honermann.net> wrote:
Enclosed is a draft of an SG16 direction paper to be discussed at our
meeting tomorrow.  It's rough, but I think in sufficient shape for
discussion.

If we manage to get through that paper, we'll discuss the paper Steve
just posted to our mailing list [1] and/or Markus' feedback paper [2].

Tom.

[1]: http://www.open-std.org/pipermail/unicode/2018-October/000144.html
[2]:
https://docs.google.com/document/d/1aI0mBcH-d3BLjs8NRHgGECbA320LGFgo-SrNJ6VnLKE/edit

_______________________________________________
SG16 Unicode mailing list
Unicode@isocpp.open-std.org
http://www.open-std.org/mailman/listinfo/unicode