[zephyrchat-cvs] zchat/ZephyrLib ZephyrMgr.cpp,1.34,1.35
Status: Alpha
Brought to you by:
akosut
|
From: <ak...@us...> - 2003-03-28 22:50:00
|
Update of /cvsroot/zephyrchat/zchat/ZephyrLib
In directory sc8-pr-cvs1:/tmp/cvs-serv6508
Modified Files:
ZephyrMgr.cpp
Log Message:
Send acks to the correct server and port.
Index: ZephyrMgr.cpp
===================================================================
RCS file: /cvsroot/zephyrchat/zchat/ZephyrLib/ZephyrMgr.cpp,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- ZephyrMgr.cpp 26 Mar 2003 17:58:55 -0000 1.34
+++ ZephyrMgr.cpp 28 Mar 2003 22:49:55 -0000 1.35
@@ -297,7 +297,7 @@
// if this is actually possible. I guess we'll just have to rely on the
// Kerberos-based checksums (which we don't check yet).
#if 0
- if (addr.fHost != GetRemoteAddr()) {
+ if (from->sin_addr.s_addr != GetRemoteAddr()) {
return;
}
#endif
@@ -308,7 +308,7 @@
case zpUNACKED:
case zpACKED:
/* client message */
- ReceiveMessage(packet, from->sin_port, from->sin_addr.s_addr);
+ ReceiveMessage(packet, from->sin_addr.s_addr, from->sin_port);
break;
case zpHMCTL:
@@ -368,7 +368,7 @@
/* We have received a packet. We should first ack it, then
* forward it to the appropriate location or queue.
*/
-
+
// Use the same headers as the original packet, but an empty body.
ZephyrPacket ack(inPacket.mHeaders, vector<string>());
// Switch the type to an ack.
|