Currently, when downcasting Actor the actor message type Maxim uses Rust's built-in TypeIDs which are not guaranteed to be the same even across the same build on different computers. Additionally they could be different between different versions of the program, which would mean that you would not be able to connect an even slightly different version of the program to a cluster of a different version of the program.
What we want to do is provide a way to solidify the type IDs, even across different versions of the program.
The unique-type-id crate sounds like the perfect solution for creating the IDs, but we need some way to hook that into the downcasting, so we might need a different crate to handle the Any type and downcasting as well.
Currently, when downcasting Actor the actor message type Maxim uses Rust's built-in TypeIDs which are not guaranteed to be the same even across the same build on different computers. Additionally they could be different between different versions of the program, which would mean that you would not be able to connect an even slightly different version of the program to a cluster of a different version of the program.
What we want to do is provide a way to solidify the type IDs, even across different versions of the program.
The
unique-type-idcrate sounds like the perfect solution for creating the IDs, but we need some way to hook that into the downcasting, so we might need a different crate to handle theAnytype and downcasting as well.