goodboy
goodboy
This is a discussion thread to dig into the theory surrounding how this project *is* (like) an *actor model* system and how it *is* or *isn't* compatible with [structured concurrency](https://trio.discourse.group/t/structured-concurrency-kickoff/55)....
After working on the built-in pubsub system I've realized it may be useful to have a (set of) synchronization decorator(s) for limiting multi-task access to user defined functions. This would...
`tractor` utilizes a simple multiplexed protocol for conducting inter-process-task-communication (IPTC)? Each per-process `trio` task can invoke tasks in other processes and received responses depending on the type of the remote...
I ran into problems trying to get channels to reliably tear down using `StreamSocket.aclose()` as per python-trio/trio/pull/460. @njsmith was very helpful in pointing out that until this is resolved streams...
This will be a better write up when I get back to it but for now just putting a link dump: #### Rx (reactive programming) - https://en.wikipedia.org/wiki/Reactive_programming - https://en.wikipedia.org/wiki/Reactive_extensions -...
`mulitprocessing`'s [forkserver](https://github.com/python/cpython/blob/master/Lib/multiprocessing/forkserver.py) has proven severely unreliable for nested process launching (#84, #134) however it is *much much faster* then our current `trio` (aka async wrapped `subprocess`) spawning backend and, as...
The list I've been meaning to look through/support: - plain old `json` (if peeps want it over `msgpack`) - [blosc](http://python-blosc.blosc.org/) - [apache arrow](https://arrow.apache.org/docs/python/index.html) - of course [protocol buffers](https://github.com/protocolbuffers/protobuf) [from google](https://developers.google.com/protocol-buffers/)...
I've already left some [notes in the code](https://github.com/tgoodlet/tractor/blob/master/tractor/_actor.py#L93) about how we could do two way streaming using the native `received = yield sent` generator semantics but it's probably worth looking...
I'm starting to realize that the way we currently allow certain python modules to have their defined functions invoked over RPC is really a form of [capabilities based security](https://en.wikipedia.org/wiki/Capability-based_security). Specifically:...
As has always been the plan (because it fits the actor model so well) we need native [zeromq](http://zguide.zeromq.org/py:all) support. This will likely need a little thinking and re-design to integrate...