Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Allow Services and Controllers to Run in Parallel #227

Closed
royce-mathew opened this issue Jul 6, 2023 · 4 comments
Closed

Allow Services and Controllers to Run in Parallel #227

royce-mathew opened this issue Jul 6, 2023 · 4 comments

Comments

@royce-mathew
Copy link

Would it be possible to create services and controllers and load them under separate actors through Knit?

It would really help if Knit supports this change internally. Because of the way that Knit is implemented, developers have little to no way of implementing Services and Controllers in parallel.

@AbstractNo
Copy link

AbstractNo commented Aug 7, 2023

I also had a similar issue. This led me to creating my own knit-like framework. Something like this can be implemented by having a seprate ThreadComm libray

This would also require a few knit "Instances" to be created for each actor.
Perhaps new methods such as "GetExternService(serviceName)" for getting services from different threads could be implemented?

@royce-mathew
Copy link
Author

Have you published this knit-like framework? How do services communicate with each other if they're in separate actors? What happens when you want to access non thread safe variables and methods?

@AbstractNo
Copy link

Since this is no longer knit related, you can private message me for more details. Just search up TritiiDumoris in users on the Roblox developer forum. I will gladly respond.

@Sleitnick
Copy link
Owner

Knit doesn't really make sense in a parallel context. Perhaps various Knit instances could run different services within different actors and communicate via SharedTables? But that would be very implementation-specific and outside the scope of Knit.

@Sleitnick Sleitnick closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants