Feature #27
encoding setting per server
| Status: | New | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 0% |
|
| Category: | Engine IRC | |||
| Target version: | - | |||
| Complexity: | Medium |
|||
| Votes: | 3 (View) |
Description
Allow to use different encodings per server. (requested by Cobrian)
Associated revisions
Revision 3a07213acabf7b0de23b9d1851781c82efb56537
[Engine/Engine-*] Refactored IProtocolManager.Connect() to use ServerModel
Cleanly pass all connection parameters to the protocol manager using the
ServerModel class. This way it is no longer needed to add and save a server
before making use of SSL options.
Also it will make it easier to add multi-identity support (references: #428),
different encoding per server (references: #27),
client certificates (references: #96) and SASL support (references: #98).
History
Updated by Jonathan Rudolph 3987 days ago
I'd relate this one to Issue 734, they could be worked on at the same time in the UI.
Updated by Jonathan Rudolph 3987 days ago
Jonathan Rudolph wrote:
I'd relate this one to Issue 944, they could be worked on at the same time in the UI.