Tcl Source Code

Channels may be configured to treat their content as encoded in one of the system encodings.  Channels which are sockets don't necessarily need the same encoding on inbound and outbound traffic.  One example is in a network server which expects requests in binary or ascii, but simultaneously tries to deliver responses in some encoded form.  HTTP is an example of a protocol in which such a pattern can easily arise.

Chans should, therefore, be able to have different read and write encodings.

A channel is only managed by a single thread at a time.

Tcl_GetChannelThread() will tell you which thread it is.

Workaround: change the encoding when switching from reading to writing. (Don't know what happens with multiple threads, so don't ask me!)