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

Investigate issues resulting from calling ref.set(..) before ref.onDisconnect().remove() #19

Open
dborkan opened this issue Apr 24, 2015 · 0 comments

Comments

@dborkan
Copy link
Contributor

dborkan commented Apr 24, 2015

Is it possible that if we call ref.set(..) before ref.onDisconnect().remove(), and something goes wrong causing set(..) to be completed but not onDisconnect().remove(), will we be stuck with data forever on the Firebase server? What happens if we swap these 2 lines?

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

No branches or pull requests

1 participant