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

Implement message bus for communication between engine components #26

Open
jstamant opened this issue Sep 25, 2016 · 0 comments
Open

Implement message bus for communication between engine components #26

jstamant opened this issue Sep 25, 2016 · 0 comments
Milestone

Comments

@jstamant
Copy link
Owner

A cleaner architecture for dealing with communication between engine components would be to implement some sort of MessageBus. All engine components would have an interface for dealing with messages on the bus. This would replace how we're using pointers to other engine components, which has the coding architecture equivalent of spaghetti.

All high-level engine components can inherit from a System class, which provides them the interface to the MessageBus. Message format, and the way that systems will interface with it will be determined upon further research and testing.

Yes, a MessageBus will most likely become a performance bottleneck down the road, but this game isn't demanding that performance yet. If a performance bottleneck is met, then maybe we'll consider revamping the engine. The MessageBus idea is just too easy to pass up at the moment.

@jstamant jstamant added this to the 0.2.0 milestone Sep 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant