Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

validate packets - not all may be meant for the client #9

Open
mvayngrib opened this issue May 22, 2015 · 6 comments
Open

validate packets - not all may be meant for the client #9

mvayngrib opened this issue May 22, 2015 · 6 comments

Comments

@mvayngrib
Copy link
Contributor

it's kind of a weird case, but I have the rudp client sharing a socket, and the rudp client ends up getting confused, misinterpreting packets not meant for itself

@shovon
Copy link
Owner

shovon commented May 22, 2015

I'm assuming the incoming packets are from the same host and port?

@mvayngrib
Copy link
Contributor Author

right

@mvayngrib
Copy link
Contributor Author

this gets me pretty far to working:

    if (this._payload.length) {
      this._acknowledgement = false;
      this._finish = false;
    } else {
      this._acknowledgement = !!(bools & 0x80);
      this._finish = !!(bools & 0x20);
    }

@shovon
Copy link
Owner

shovon commented May 22, 2015

That's in Packet.js?

@shovon
Copy link
Owner

shovon commented May 22, 2015

Bear in mind, I'm absolutely open to fixing this problem.

Just trying to be on the same page about ways to tackling this.

@mvayngrib
Copy link
Contributor Author

yep, Packet.js :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants