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.

Sign up for GitHub

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

Jump to bottom

Find out whether there is any way we can have nextTick back again as right now it does what enqueueTick does #54

Open
yrashk opened this issue Jan 7, 2011 · 1 comment
Open

Find out whether there is any way we can have nextTick back again as right now it does what enqueueTick does #54

yrashk opened this issue Jan 7, 2011 · 1 comment
Labels
idea

Comments

@yrashk
Copy link
Member

yrashk commented Jan 7, 2011

The only idea I have so far is two have two pairs of push/pull sockets per VM and make ticker poll the "emergency" queue first. And this emergency queue is for next ticks, as opposed to enqueued ticks.
@yrashk
Copy link
Member Author

yrashk commented Jan 7, 2011

Or is it a bad idea to have an emergency/priority ticking anyway? Something to think about. May be there is no need in it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
idea
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yrashk