Overview
| Artifact ID: | 4aec98d545b55cfc23ce1f7f9a535042b66d6891 |
|---|---|
| Ticket: | a67f00204cf2abfa82f9bf8e5a4a363e1ec58a99
chan encoding needs to be per-direction |
| User & Date: | cmcc 2014-03-20 19:39:01 |
Changes
- assignee changed to: "nobody"
- closer changed to: "nobody"
- cmimetype changed to: "text/plain"
- comment changed to:
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.
- foundin changed to: "all"
- is_private changed to: "0"
- login: "cmcc"
- priority changed to: "5 Medium"
- private_contact changed to: "16910d69b11045755316a073070779a85cd9218f"
- resolution changed to: "None"
- severity changed to: "Minor"
- status changed to: "Open"
- submitter changed to: "cmcc"
- subsystem changed to: "25. Channel System"
- title changed to: "chan encoding needs to be per-direction"
- type changed to: "RFE"