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

Non connected transport skip peer acceptance basic rules #47

Open
cheme opened this issue Mar 22, 2015 · 1 comment
Open

Non connected transport skip peer acceptance basic rules #47

cheme opened this issue Mar 22, 2015 · 1 comment

Comments

@cheme
Copy link
Owner

cheme commented Mar 22, 2015

Non connected transport do not validate the peer (no persistence of peer, stateless so we do not have challenge anymore). Plan would be to have a new query type for ping (usefull also for synch where we always stuck client process waiting synchrously for a pong see [https://github.com//issues/41].

Other plan should be to symply drop non connected transport (make things a bit more complicated and currently not used). See also ref to APONG

@cheme
Copy link
Owner Author

cheme commented Nov 22, 2015

This will not be the case anymore as soon as Shadow message are added to those transport (requires persistence of crypter/transport address)

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

No branches or pull requests

1 participant