From f13493edb2aae228ddbe70cc2f0609c541faf2d7 Mon Sep 17 00:00:00 2001 From: Adam Ierymenko Date: Mon, 31 Mar 2014 22:23:55 -0700 Subject: Oops... turns out we need to differentiate incoming from outgoing TCP and indeed learn incoming TCP paths. Otherwise the recipient of a TCP connection does not know to reply via TCP! Heh. --- node/TcpSocket.hpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'node/TcpSocket.hpp') diff --git a/node/TcpSocket.hpp b/node/TcpSocket.hpp index ea2b0ddf..8a9a7095 100644 --- a/node/TcpSocket.hpp +++ b/node/TcpSocket.hpp @@ -71,11 +71,11 @@ public: protected: #ifdef __WINDOWS__ - TcpSocket(SocketManager *sm,SOCKET s,bool c,const InetAddress &r) : + TcpSocket(SocketManager *sm,SOCKET s,Socket::Type t,bool c,const InetAddress &r) : #else - TcpSocket(SocketManager *sm,int s,bool c,const InetAddress &r) : + TcpSocket(SocketManager *sm,int s,Socket::Type t,bool c,const InetAddress &r) : #endif - Socket(Socket::ZT_SOCKET_TYPE_TCP,s), + Socket(t,s), _lastActivity(Utils::now()), _sm(sm), _outbuf((unsigned char *)0), -- cgit v1.2.3