forked from I2P_Developers/i2p.i2p
benchmarking large messages doesnt make much sense when we can compress the payload really really well, now does it?
This commit is contained in:
@@ -11,6 +11,7 @@ import java.util.Date;
|
|||||||
import java.util.Properties;
|
import java.util.Properties;
|
||||||
|
|
||||||
import net.i2p.I2PException;
|
import net.i2p.I2PException;
|
||||||
|
import net.i2p.I2PAppContext;
|
||||||
import net.i2p.client.I2PClient;
|
import net.i2p.client.I2PClient;
|
||||||
import net.i2p.client.I2PClientFactory;
|
import net.i2p.client.I2PClientFactory;
|
||||||
import net.i2p.client.I2PSession;
|
import net.i2p.client.I2PSession;
|
||||||
@@ -219,7 +220,8 @@ class I2PAdapter {
|
|||||||
DataHelper.writeDate(baos, new Date(now));
|
DataHelper.writeDate(baos, new Date(now));
|
||||||
int padding = size - baos.size();
|
int padding = size - baos.size();
|
||||||
byte paddingData[] = new byte[padding];
|
byte paddingData[] = new byte[padding];
|
||||||
Arrays.fill(paddingData, (byte) 0x2A);
|
I2PAppContext.getGlobalContext().random().nextBytes(paddingData);
|
||||||
|
//Arrays.fill(paddingData, (byte) 0x2A);
|
||||||
DataHelper.writeLong(baos, 2, padding);
|
DataHelper.writeLong(baos, 2, padding);
|
||||||
baos.write(paddingData);
|
baos.write(paddingData);
|
||||||
boolean sent = _session.sendMessage(peer, baos.toByteArray());
|
boolean sent = _session.sendMessage(peer, baos.toByteArray());
|
||||||
|
Reference in New Issue
Block a user