Change order of argument for createPayload
Expecting data first and metadata second aligns better with the single arg variant that accepts data. This is also consistent with the RSocket API in the create methods of ByteBufPayload and DefaultPayload.
This commit is contained in:
@@ -235,7 +235,7 @@ final class DefaultRSocketRequester implements RSocketRequester {
|
||||
DataBufferUtils.release(data);
|
||||
throw ex;
|
||||
}
|
||||
return PayloadUtils.createPayload(metadata, data);
|
||||
return PayloadUtils.createPayload(data, metadata);
|
||||
}
|
||||
|
||||
private Mono<Payload> emptyPayload() {
|
||||
|
||||
@@ -202,7 +202,7 @@ final class DefaultRSocketRequesterBuilder implements RSocketRequester.Builder {
|
||||
}
|
||||
metadata = metadata != null ? metadata : emptyBuffer(strategies);
|
||||
data = data != null ? data : emptyBuffer(strategies);
|
||||
return PayloadUtils.createPayload(metadata, data);
|
||||
return PayloadUtils.createPayload(data, metadata);
|
||||
}
|
||||
|
||||
private DataBuffer emptyBuffer(RSocketStrategies strategies) {
|
||||
|
||||
@@ -72,11 +72,11 @@ public abstract class PayloadUtils {
|
||||
* or using {@link Unpooled#wrappedBuffer(ByteBuffer...)} if necessary.
|
||||
* Otherwise, if both are {@link DefaultDataBuffer}, then
|
||||
* {@link DefaultPayload} is created.
|
||||
* @param metadata the metadata part for the payload
|
||||
* @param data the data part for the payload
|
||||
* @param metadata the metadata part for the payload
|
||||
* @return the created payload
|
||||
*/
|
||||
public static Payload createPayload(DataBuffer metadata, DataBuffer data) {
|
||||
public static Payload createPayload(DataBuffer data, DataBuffer metadata) {
|
||||
return data instanceof NettyDataBuffer || metadata instanceof NettyDataBuffer ?
|
||||
ByteBufPayload.create(asByteBuf(data), asByteBuf(metadata)) :
|
||||
DefaultPayload.create(asByteBuffer(data), asByteBuffer(metadata));
|
||||
|
||||
Reference in New Issue
Block a user