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

New API endpoints #173

Closed
4 tasks done
cpvalente opened this issue Jul 2, 2022 · 2 comments
Closed
4 tasks done

New API endpoints #173

cpvalente opened this issue Jul 2, 2022 · 2 comments
Labels
feature New feature or request

Comments

@cpvalente
Copy link
Owner

cpvalente commented Jul 2, 2022

This one is preparing for #55, also answering some popular requests here

We need a few new endpoints, both in HTTP, websockets and OSC

Possibility to load a specific event

  • endpoint: <"loadEvent"> payload event <eventIndex>
  • endpoint: <"loadEventById"> payload event <eventId>

Possibility to start a specific event

  • endpoint: <"startEvent"> payload event <eventIndex>
  • endpoint: <"startEventById"> payload event <eventId>

Note: event indexes in APIs are 1 based

@cpvalente cpvalente added the feature New feature or request label Jul 2, 2022
@je71175
Copy link

je71175 commented Jul 3, 2022

Would it be possible to use this functionality to synchronise 2 separate instances of onTime - i am thinking of a production and backup instance - for example once is triggered on the production server, it makes an web or OSC call/message to the backup onTime so start the same ...

@cpvalente
Copy link
Owner Author

Hi @je71175 , I am unsure on how this could work and a feature like that should be planned with some care.
I will move this into a separate issue #174

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants