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

[FEATURE] Schedule messages for delivery #55

Open
imyousuf opened this issue Jan 13, 2021 · 0 comments
Open

[FEATURE] Schedule messages for delivery #55

imyousuf opened this issue Jan 13, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@imyousuf
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Instead of instant dispatch we want the ability to schedule a message at a future time. This message should be deleteable before its dispatched. And schedule can be one time or repeated; in case of repeated it can be specified how many times or till when.

Describe the solution you'd like
Introduce a new concept of "ScheduledMessage" which will have a dispatchDate specified; additionally if cron is specified it has to be accompanied with times or until and not both.

Describe alternatives you've considered
Until this functionality is available clients will have to create their own scheduler for this purpose; but that seems too much and hence we will implement it.

@imyousuf imyousuf added the enhancement New feature or request label Jan 13, 2021
@imyousuf imyousuf added this to the v0.2 milestone Jan 13, 2021
@imyousuf imyousuf added this to Backlog in Broker Board via automation Jan 21, 2021
@imyousuf imyousuf modified the milestones: v0.2, v0.3 Jul 27, 2021
@imyousuf imyousuf modified the milestones: v0.3, v0.2 Sep 25, 2021
@imyousuf imyousuf self-assigned this Sep 25, 2021
@imyousuf imyousuf modified the milestones: v0.2, v0.3 Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant