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

Consider adding time-related events and their generation #33

Open
alexander-yevsyukov opened this issue Jul 12, 2018 · 2 comments
Open

Comments

@alexander-yevsyukov
Copy link
Contributor

Client-side code can benefit from responding to TimeZoneChanged, so that it can create new ActorRequestFactory with new zoneOffset and zoneId.

Server-side business logic can be interested in having calendar-related events like:
YearStarted, MonthStarted, WeekStarted, DayStarted. HourStarted.

Implementations would depend on server infrastructure, and be subject of re-visiting scheduling commands.

@alexander-yevsyukov
Copy link
Contributor Author

Here's what Vaughn Vernon says about the topic.

@alexander-yevsyukov
Copy link
Contributor Author

@armiol, I think we need scheduling for events too:

  1. It would be needed for emitting general events like described above.
  2. It would save time on converting general events into domain ones.

The second thing would be helpful for saving manual labor on obvious things. For example, FiscalYearEnded may occur every end of March. If we can just say it in event declaration options, we'd save on creating a stateless event handler that would convert MonthEnded with month=MARCH into FiscalYearEnded.

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