-
Notifications
You must be signed in to change notification settings - Fork 27
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
Support DPUB to send deferred messages #23
Conversation
@Soulou, thanks for your PR! By analyzing the blame information on this pull request, we identified @bschwartz and @freerobby to be potential reviewers |
Hi Soulou! Thanks for the PR! It looks great, and thanks for updating the README too. A few questions: What do you think about making Also, should it take seconds or milliseconds as its argument? Feeling divided on that. Seconds seems more Ruby-esque I suppose. Any thoughts @freerobby? |
@Soulou any thoughts on using seconds as an arg instead of a time for |
I agree that seconds sounds much more ruby-esque as you can do No problem to edit the README, sorry for the delay between the PR and my reaction :-) |
We could use sidekiq model and using a float (which is multiplied by 1000 before sending the command) As a result, both would work:
|
Love the float idea. Good thinking! On Wednesday, June 22, 2016, Soulou notifications@github.com wrote:
|
Ok I'll handle it when I've a few minutes :) |
Done ! |
Thanks @Soulou. Looks good to me! Going to merge this, bump the version, and publish to ruby gems. |
Sorry I'm late to the party on this! Thanks @Soulou for contributing here, agree with both of you that seconds works nicely for the ruby client! |
Bumped to 1.7.0 and released on Rubygems. Thanks again for this @Soulou! |
No description provided.