RemoteAuxPort for SuperClassic and regular Classic [CORE2263]

[firebird-automations]

Submitted by: Zd (zd)

SuperClassic should listen to events on a single RemoteAuxPort port just like SuperServer does.

Otherwise applications that connect to the database over the Internet (and use Firewalls or a secure tunnel) can't use events or are forced to to use SuperServer, which doesn't support multiple processors at all...

Since events are a very important feature of Firebird, this issue should be fixed as soon as possible.

Commits: ae1de3f

[firebird-automations]

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

[firebird-automations]

Modified by: @dyemanov

priority: Blocker [ 1 ] => Major [ 3 ]

[firebird-automations]

Modified by: @dyemanov

Version: 2.1.1 [ 10223 ]

Version: 2.0.4 [ 10211 ]

Version: 2.1.0 [ 10041 ]

Version: 2.0.3 [ 10200 ]

Version: 2.0.2 [ 10130 ]

Version: 2.0.1 [ 10090 ]

Version: 2.0.0 [ 10091 ]

[firebird-automations]

Commented by: @asfernandes

Should not the description be changed to [Super]Classic then?
There was no 2.0 and 2.1 SuperClassic. :-)

[firebird-automations]

Modified by: @dyemanov

summary: RemoteAuxPort for SuperClassic => RemoteAuxPort for SuperClassic and regular Classic

[firebird-automations]

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

[firebird-automations]

Modified by: @dyemanov

status: In Progress [ 3 ] => Open [ 1 ]

[firebird-automations]

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10300 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test

[firebird-automations]

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested