Completely factor out "desperation" from the core. I thought of a significantly simpler way to move all of this logic entirely into the containing service, liberating the core from any concern over the nature of its pipe to the outside world.

1 files changed, 1 insertions, 4 deletions

diff --git a/node/IncomingPacket.hpp b/node/IncomingPacket.hpp
index 5940a78e..174fa38d 100644
--- a/node/IncomingPacket.hpp
+++ b/node/IncomingPacket.hpp
@@ -73,15 +73,13 @@ public:
 	 * @param data Packet data
 	 * @param len Packet length
 	 * @param remoteAddress Address from which packet came
-	 * @param linkDesperation Link desperation for link over which packet was received
 	 * @param now Current time
 	 * @throws std::out_of_range Range error processing packet
 	 */
-	IncomingPacket(const void *data,unsigned int len,const InetAddress &remoteAddress,unsigned int linkDesperation,uint64_t now) :
+	IncomingPacket(const void *data,unsigned int len,const InetAddress &remoteAddress,uint64_t now) :
  		Packet(data,len),
  		_receiveTime(now),
  		_remoteAddress(remoteAddress),
- 		_linkDesperation(linkDesperation),
  		__refCount()
 	{
 	}
@@ -129,7 +127,6 @@ private:
 
 	uint64_t _receiveTime;
 	InetAddress _remoteAddress;
-	unsigned int _linkDesperation;
 	AtomicCounter __refCount;
 };