Android RealTimeMultiplayer.sendReliableMessage消息接收顺序错误
我正在使用Games.RealTimeMultiplayer.sendReliableMessage在Android上发送消息,但它们似乎出现了故障。各国: 可靠的消息传递。通过可靠的消息传递,可以保证数据传递、完整性和顺序 我将一个大数据包分解为多个1400字节的消息,并使用sendReliableMessage发送每个消息,这是在一个循环中完成的。在该循环之后,我使用sendReliableMessage发送另一条消息,但在接收设备上,最后一条消息在其他一些消息之前通过。发送数据包的代码为:Android RealTimeMultiplayer.sendReliableMessage消息接收顺序错误,android,google-play-services,Android,Google Play Services,我正在使用Games.RealTimeMultiplayer.sendReliableMessage在Android上发送消息,但它们似乎出现了故障。各国: 可靠的消息传递。通过可靠的消息传递,可以保证数据传递、完整性和顺序 我将一个大数据包分解为多个1400字节的消息,并使用sendReliableMessage发送每个消息,这是在一个循环中完成的。在该循环之后,我使用sendReliableMessage发送另一条消息,但在接收设备上,最后一条消息在其他一些消息之前通过。发送数据包的代码为:
public void sendPacket(Packet packet)
{
try {
Log.d(getPackageName(), "Sending packet: " + packet.getClass().getSimpleName());
ByteArrayOutputStream byteOutpuStream = new ByteArrayOutputStream();
ObjectOutputStream outputStream = new ObjectOutputStream(byteOutpuStream);
outputStream.writeObject(packet);
byte[] bytes = byteOutpuStream.toByteArray();
outputStream.close();
if(m_Participants != null) {
for (Participant participant : m_Participants) {
if (participant.getParticipantId().equals(m_LocalParticipantID) == false) {
Log.d(getPackageName(), "Sending object size " + bytes.length + " to participant " + participant.getParticipantId());
byte[] objectSize = ByteBuffer.allocate(4).putInt(bytes.length).array();
int sendResult = Games.RealTimeMultiplayer.sendReliableMessage(m_GoogleClient, this, objectSize, m_RoomID, participant.getParticipantId());
Log.d(getPackageName(), "Send object size result: " + sendResult);
Log.d(getPackageName(), "Sending packet to " + participant.getParticipantId());
int bytesRemaining = bytes.length;
if(bytesRemaining <= Multiplayer.MAX_RELIABLE_MESSAGE_LEN)
{
Log.d(getPackageName(), "Sending full packet " + bytesRemaining + " bytes");
sendResult = Games.RealTimeMultiplayer.sendReliableMessage(m_GoogleClient, this, bytes, m_RoomID, participant.getParticipantId());
Log.d(getPackageName(), "Send packet result: " + sendResult);
}
else
{
int sentAmount = 0;
byte[] bufferToSend = new byte[Multiplayer.MAX_RELIABLE_MESSAGE_LEN];
while(bytesRemaining > 0) {
int byteCountSent = 0;
if(bytesRemaining >= Multiplayer.MAX_RELIABLE_MESSAGE_LEN)
{
byteCountSent = Multiplayer.MAX_RELIABLE_MESSAGE_LEN;
for(int byteIndex = 0; byteIndex < byteCountSent; ++byteIndex)
{
bufferToSend[byteIndex] = bytes[sentAmount + byteIndex];
}
}
else
{
byteCountSent = bytesRemaining;
bufferToSend = Arrays.copyOfRange(bytes, sentAmount, sentAmount + bytesRemaining);
}
Log.d(getPackageName(), "Sending " + bufferToSend.length + " bytes");
sendResult = Games.RealTimeMultiplayer.sendReliableMessage(m_GoogleClient, this, bufferToSend, m_RoomID, participant.getParticipantId());
Log.d(getPackageName(), "Send packet result: " + sendResult);
bytesRemaining -= byteCountSent;
sentAmount += byteCountSent;
}
}
}
}
}
}
catch(Exception e)
{
e.printStackTrace();
}
接收函数是,它获取4字节的数据包大小,然后在消息传入时重新组装数据包,如下所示:
First call to sendPacket:
Sending object size 62234 to participant p_CImSt4aNy73IiQEQAQ
Send object size result: 1
Sending packet to p_CImSt4aNy73IiQEQAQ
Sending 1400 bytes
Send packet result: 2
Sending 1400 bytes
Send packet result: 3
Sending 1400 bytes
...
Send packet result: 44
Sending 1400 bytes
Send packet result: 45
Sending 634 bytes
Send packet result: 46
Next call to sendPacket:
Sending packet: StartGamePacket
Sending object size 267 to participant p_CImSt4aNy73IiQEQAQ
Send object size result: 47
Sending packet to p_CImSt4aNy73IiQEQAQ
Sending full packet 267 bytes
Send packet result: 48
@Override
public void onRealTimeMessageReceived(RealTimeMessage realTimeMessage)
{
try {
byte[] data = realTimeMessage.getMessageData();
Log.d(getPackageName(), "onRealTimeMessageReceived: " + data.length + " bytes");
// Are we expecting a packet?
if(m_CurrentPacketData == null)
{
// Get the packet size
if(data.length != 4)
{
Log.d(getPackageName(), "Error! 4 bytes expected for packet size, got " + data.length);
}
else
{
int packetSize = ByteBuffer.wrap(data).getInt();
m_CurrentPacketData = new byte[packetSize];
m_CurrentPacketReceiveCount = 0;
}
}
else
{
// Append the data to the packet
Log.d(getPackageName(), "Received data of " + data.length + " bytes");
for(int byteIndex = 0; byteIndex < data.length; ++byteIndex)
{
m_CurrentPacketData[m_CurrentPacketReceiveCount + byteIndex] = data[byteIndex];
}
m_CurrentPacketReceiveCount += data.length;
// Have we received it all?
if(m_CurrentPacketReceiveCount == m_CurrentPacketData.length)
{
Log.d(getPackageName(), "Full packet received");
ByteArrayInputStream byteInputStream = new ByteArrayInputStream(m_CurrentPacketData);
ObjectInputStream inputStream = new ObjectInputStream(byteInputStream);
Packet packet = (Packet) inputStream.readObject();
inputStream.close();
m_ReceivedPackets.add(packet);
Log.d(getPackageName(), "Packet received: " + packet.getClass().getSimpleName());
m_CurrentPacketData = null;
m_CurrentPacketReceiveCount = 0;
processReceivedPackets();
}
else
{
Log.d(getPackageName(), "Still " + (m_CurrentPacketData.length - m_CurrentPacketReceiveCount) + " bytes remaining");
}
}
}
catch (Exception e)
{
e.printStackTrace();
}
}
正如您在接近尾声时所看到的,数据包的顺序出现了问题。安卓上的实时多人游戏还有其他人遇到过这样的问题吗?你解决了这个问题吗?
看来实施并不能保证秩序。因此,您可能要做的是检查此消息id的重新回调结果(
onRealTimeMessageSent
)(称为令牌并由sendReliableMessage
重新调谐),并且只有当结果正常时,才发送下一个数据包。我最终更改了数据包结构,在报头中包含一个id,该id随着每个数据包的增加而增加,这样,接收方就可以跟踪数据包的顺序,并对无序到达的数据包重新排序。这比等待每个数据包的确认要快一点。我想你是对的,要么是实现中存在缺陷,要么是文档不正确。同样的问题也发生在我身上,经过一些测试,我得出结论,sendReliableMessage
不能保证数据包以相同的顺序传递。我刚刚决定等待onRealTimeMessageSent
回调,以在发件人端强制执行排序。您能否与您的解决方案共享一个示例?(即,“最终改变数据包结构,在报头中包含一个ID,该ID随着每个数据包的增加而增加,以便接收方能够跟踪数据包的顺序,并对无序到达的数据包重新排序。”)
onRealTimeMessageReceived: 4 bytes
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 60834 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 59434 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 58034 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 56634 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 55234 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 53834 bytes remaining
...
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 17434 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 16034 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 14634 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 13234 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 11834 bytes remaining
onRealTimeMessageReceived: 634 bytes
Received data of 634 bytes
Still 11200 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 9800 bytes remaining
onRealTimeMessageReceived: 4 bytes
Received data of 4 bytes
Still 9796 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 8396 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 6996 bytes remaining
onRealTimeMessageReceived: 267 bytes
Received data of 267 bytes
Still 6729 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 5329 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 3929 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 2529 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes
Still 1129 bytes remaining
onRealTimeMessageReceived: 1400 bytes
Received data of 1400 bytes