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

AngularActor events dropped if sent prior to angular initialization #1

Closed
joescii opened this issue Mar 5, 2014 · 2 comments
Closed
Assignees
Labels

Comments

@joescii
Copy link
Owner

joescii commented Mar 5, 2014

It appears that in some cases an AngularActor which quickly emits/broadcasts an event possibly while angular is still loading, that event is never handed by the listeners.

@joescii joescii added the bug label Mar 5, 2014
@joescii joescii self-assigned this Mar 5, 2014
@joescii
Copy link
Owner Author

joescii commented Mar 17, 2014

It seems in some cases comet will eventually retry the messages, and they are all received in order as expected. Perhaps we could use our random ID to create a queue on the client for holding these messages until angular returns a scope for our actor. In the meantime, I'm going to regard this as not terribly important.

@joescii
Copy link
Owner Author

joescii commented Jul 3, 2014

Resolved in version 0.4.5

@joescii joescii closed this as completed Jul 3, 2014
joescii added a commit that referenced this issue Jul 5, 2014
joescii added a commit that referenced this issue Jul 27, 2014
…reviously would only dequeue once a new message arrived.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant