Add better response encoding options to the TCP connectors

[rbeckman-nextgen]

Right now the charset encoding setting on the TCP connectors acts on both the incoming data and outgoing data. When you set Data Type to Binary mode, that has different effects on the listener and sender. On the TCP Listener, Binary mode acts on both the incoming message and outgoing response, but on the TCP Sender it only acts on the outgoing message and not on the incoming response.

Basically the encoding rules for the incoming/outgoing data should be separated to give the user more control. Right now you have to do weird charset hacks if you want to, for example, send data out according to one charset, but receive a response according to a different charset. Or, if you want to send textual data out, but receive a binary response.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-3757
Reporter: narupley
Created: 2015-08-14T08:58:00.000-0700