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

[INFO]: network graphs 0.1.9 vs 0.1.10 #584

Closed
zoff99 opened this issue Aug 25, 2017 · 13 comments
Closed

[INFO]: network graphs 0.1.9 vs 0.1.10 #584

zoff99 opened this issue Aug 25, 2017 · 13 comments
Labels
meta Process related network Network P3 Low priority
Milestone

Comments

@zoff99
Copy link

zoff99 commented Aug 25, 2017

No description provided.

@zoff99
Copy link
Author

zoff99 commented Aug 25, 2017

v0.1.9

v0 1 9__wlan

@zoff99
Copy link
Author

zoff99 commented Aug 25, 2017

v0.1.10

v0 1 10__wlan

@nurupo
Copy link
Member

nurupo commented Aug 25, 2017

Nice. This is not the final result though, based on what @zugz has said in #542, we will start to see the difference once majority of the network switches to 0.1.10, which didn't happen yet.

Edit: mentioned the wrong person

@zugz
Copy link

zugz commented Aug 26, 2017 via email

@zoff99
Copy link
Author

zoff99 commented Aug 26, 2017

tcp relay. 4 friends (online)

@zugz
Copy link

zugz commented Aug 26, 2017 via email

@zoff99
Copy link
Author

zoff99 commented Aug 26, 2017

about 10 minutes in

@zoff99
Copy link
Author

zoff99 commented Aug 26, 2017

anybody with good knowledge about tcp relay code get in touch with me please
@zugz i want to tweak the tcp relay code to make it more mobile friendly, but need some help

@zugz
Copy link

zugz commented Aug 26, 2017 via email

@zugz
Copy link

zugz commented Aug 26, 2017 via email

@iphydf
Copy link
Member

iphydf commented Jan 16, 2018

@zugz what is the idea?

@zugz
Copy link

zugz commented Jan 17, 2018 via email

@ghost
Copy link

ghost commented Feb 5, 2018

Whilst this is a great reduction what I don't get is why don't we use a reactive system where a node coming up sends an update to all it's contacts and conversely sends a down update to all it's contacts and does no polling other than if it has a message in it's out queue for a node that is not responding.. This would make a seriously large impact to idle traffic and cpu loads. What do you all think? I mean if all the polling is just to let someone know if people are online - which in most case we do not give a hoot about until we want to communicate with them, is a huge waste of data allowance and battery energy. I know that currently there is no outbound queue but yeah we need it big time....pls.

@SkyzohKey SkyzohKey added network Network meta Process related labels Feb 13, 2018
@iphydf iphydf added this to the v0.2.x milestone Jul 16, 2018
@zoff99 zoff99 closed this as completed Nov 4, 2018
@robinlinden robinlinden modified the milestones: v0.2.x, v0.2.9 Jan 3, 2019
@iphydf iphydf added the P3 Low priority label Feb 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Process related network Network P3 Low priority
Projects
None yet
Development

No branches or pull requests

6 participants