8000 Defer entire initial connection rather than just the disconnect by kenhkan · Pull Request #69 · noflo/noflo · GitHub
[go: up one dir, main page]

Skip to content

Defer entire initial connection rather than just the disconnect - #69

Merged
bergie merged 1 commit into
noflo:masterfrom < 8000 div class="d-flex flex-items-center overflow-hidden gap-1">kenhkan:send_initials_on_next_tick
Apr 26, 2013
Merged

bergie merged 1 commit into
noflo:masterfrom
kenhkan:send_initials_on_next_tick

Conversation

@kenhkan
@kenhkan kenhkan commented Apr 25, 2013
Copy link
Copy Markdown
Contributor

The entire connection should be deferred until next tick to avoid segmenting data packets and disconnect signal within the same connection.

…menting data packets and disconnect signal within the same connection
bergie added a commit that referenced this pull request Apr 26, 2013
Defer entire initial connection rather than just the disconnect
@bergie
bergie merged commit 0fbcccd into noflo:master Apr 26, 2013
@kenhkan
kenhkan deleted the send_initials_on_next_tick branch April 26, 2013 16:57
kenhkan added a commit to kenhkan/noflo that referenced this pull request May 1, 2013
Checking for downstream readiness was initially a problem as described in noflo#40. That was due to initial packets being sent before the network is ready. It's partially solved in noflo#69 when initial packets are only sent upon the respective network has been loaded. This PR solves the other half which is initial packets being sent in order of the programmer's specification so by the time the network is run, everything should be ready anyway.
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

Successfully merging this pull request may close these issues.

2 participants

0