Toying with a message type for "object references" #294
Labels
discussion
experiment
Exploratory design and testing
IPC and transport
messaging
messaging patterns and protocols
question
Further information is requested
As a future requirement and probably large convenience for many users looking to "pass around remote python objects" (in a message native way) in actors (#191, #5) i've started toying with some ideas for making a built-in message-serialization compatible type that we can offer as part of our public sugar apis.
The main set of tools include
msgpack
type extensions (since that's our only official codec atm):pkgutils.resolve_name()
resolver in py 3.9I have a draft implementation for a
str
derivative which gets us a nice compact api for conversion betweenstr
andobject
references and could likely be integrated with ourenable_modules:list[str]
"module capability per actor" system to get us moving in the cap-based-sec direction.I'll put up a matching PR shortly 😎
The text was updated successfully, but these errors were encountered: