lnwire: remove unused MaxMessagePayload const

MaxMessagePayload and MaxSliceLength are duplicate variables. This
commit deletes MaxMessagePayload and keeps MaxSliceLength.
This commit is contained in:
yyforyongyu 2021-06-17 10:49:33 +08:00
parent 90db8de6fe
commit 4b12f40a48
No known key found for this signature in database
GPG Key ID: 9BCD95C4FF296868
3 changed files with 2 additions and 6 deletions

View File

@ -7,7 +7,7 @@ import (
// ReadSize represents the size of the maximum message that can be read off the
// wire by brontide. The buffer is used to hold the ciphertext while the
// brontide state machine decrypts the message.
const ReadSize = lnwire.MaxMessagePayload + 16
const ReadSize = lnwire.MaxSliceLength + 16
// Read is a static byte array sized to the maximum-allowed Lightning message
// size, plus 16 bytes for the MAC.

View File

@ -7,7 +7,7 @@ import (
// WriteSize represents the size of the maximum plaintext message than can be
// sent using brontide. The buffer does not include extra space for the MAC, as
// that is applied by the Noise protocol after encrypting the plaintext.
const WriteSize = lnwire.MaxMessagePayload
const WriteSize = lnwire.MaxSliceLength
// Write is static byte array occupying to maximum-allowed plaintext-message
// size.

View File

@ -12,10 +12,6 @@ import (
"io"
)
// MaxMessagePayload is the maximum bytes a message can be regardless of other
// individual limits imposed by messages themselves.
const MaxMessagePayload = 65535 // 65KB
// MessageType is the unique 2 byte big-endian integer that indicates the type
// of message on the wire. All messages have a very simple header which
// consists simply of 2-byte message type. We omit a length field, and checksum