|
Just committing this warning, because I want to know if the problem really affects us
|
Matthew Wild |
Sat, 08 Nov 2008 20:39:08 +0000 |
|
Added resource priority handling, etc
|
Waqas Hussain |
Sun, 02 Nov 2008 06:36:42 +0500 |
|
Fix s2s once and for all
|
Matthew Wild |
Sat, 01 Nov 2008 21:07:14 +0000 |
|
General fixes for s2s, to make it more robust (I hope), sending data to remote hosts sane (s2ssession.send() works as expected), recycle outgoing dialback connections, etc.
|
Matthew Wild |
Sat, 01 Nov 2008 18:28:46 +0000 |
|
sends2s -> s2s_session.send(), s2s_session.send() -> s2s_session.sends2s()
|
Matthew Wild |
Thu, 30 Oct 2008 21:11:22 +0000 |
|
Better logging of s2s connections
|
Matthew Wild |
Sun, 26 Oct 2008 14:03:40 +0000 |
|
Little tweak for more useful logging of closed s2s sessions
|
Matthew Wild |
Sun, 26 Oct 2008 13:14:14 +0000 |
|
Remove misleading log message regarding s2s/dialback
|
Matthew Wild |
Sat, 25 Oct 2008 18:21:34 +0100 |
|
other half of previous commit
|
Matthew Wild |
Fri, 24 Oct 2008 18:14:40 +0100 |
|
Remove some overly-verbose debug log output
|
Matthew Wild |
Fri, 24 Oct 2008 15:33:38 +0100 |
|
Destroy s2s sendqueue when connection is established successfully and data written
|
Matthew Wild |
Fri, 24 Oct 2008 15:32:31 +0100 |
|
Hack until we get SRV resolving
|
Matthew Wild |
Fri, 24 Oct 2008 14:59:04 +0100 |
|
s2s works! \o/ \o/
s2s
|
Matthew Wild |
Fri, 24 Oct 2008 07:27:36 +0100 |
