mantra

flexibility of message handling. Direct routing requires:

a) That the client create their own message class derived from direct_message.

b) That any task handling said message class knows about it's lifetime charateristics.

c) That any task handling said message override do_message for direct_message.

Benchmarks show direct routing can be MUCH faster than standard routing,

(10-15 times faster in some cases), however standard messgaes are still

recommended where this kind of performance is not required or for portabiliy.

And allowed for users to also add speical handling for any other types they deem necessary.

third party users that use tracing to disable it entirely

from their code for unit testing and such.

two threads to try and close socket at the same time, and one

of them will then raise an exception and cause a core.

the PTY, which is not being read yet by the session (telnet

specifically). Changed it so that editline is not even

initalized until editline_session::run(), which means it is

in it's own thread, and AFTER the pty's other end is being

read by the service. This stops telnet blocking the service

handler if it only has one thread and termcap is b0rked.

conflict between editline and socket sessions.

service (or trying to do latency check if no threads are active).

Also fixed problem where formatting was not properly applied

because we were invoking the formatter callback by value instead

of reference (caused a core).

tweaks like adding the name of the last route on exception.