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

Separate EDDI and the VoiceAttack plugin into two separate applications which communicate via an API #2690

Open
Tkael opened this issue Jan 18, 2025 · 0 comments
Labels
9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin'

Comments

@Tkael
Copy link
Member

Tkael commented Jan 18, 2025

What happens now

EDDI's framework version cannot be upgraded without creating incompatibility with the current version of VoiceAttack.

What I'd like to happen

Separate EDDI and the VoiceAttack plugin into two separate applications which communicate via an API.
This would allow EDDI and VoiceAttack plugin versions to be upgraded separately from one another.

How it can happen

https://learn.microsoft.com/en-us/aspnet/core/grpc/interprocess?view=aspnetcore-8.0
https://learn.microsoft.com/en-us/aspnet/core/grpc/?view=aspnetcore-8.0
https://learn.microsoft.com/en-us/aspnet/core/grpc/performance?view=aspnetcore-8.0

EDDI Version

4.1.0-b3

@Tkael Tkael added 9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin' labels Jan 18, 2025
@Tkael Tkael mentioned this issue Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
9. enhancement The behaviour is as specified, but we would like to modify or extend the spec. significant work Just sayin'
Projects
None yet
Development

No branches or pull requests

1 participant