forums.smartfoxserver.com

I have send the test project to the support email.There is not a viable solution so far, is really frustrating.

Please check your email.
We have replied to you on May 2nd.

Thanks

Lapo wrote:Please check your email.
We have replied to you on May 2nd.

Thanks

It is hard to avoid send more than one request at the same time.Why the client couldn't drop the message and continue to prase data after crash,at least this can reduce the negative impact of the BUG .

Honestly it's not hard to do that, and in theory it doesn't make any sense to send concurrent requests.

Why the client couldn't drop the message and continue to prase data after crash,at least this can reduce the negative impact of the BUG .

For a very simple reason. The packets is a stream of bytes, if you push the client to the limit and cause a network error the client has no way to know where the data of the next packet is positioned in the stream because the previous packet is corrupted. A51 already explained this in his previous post.

As I recommended earlier try sending the requests one after the other if they require a response (by waiting for each server reply)
Otherwise just send the three as one request.