JuliaLang / JuliaLang/Distributed.jl
Define and implement a routable, extensible Julia "message"
Open
@amitmurthy is already working on this.
Since Jul 7, 2015.
- Dominant language
- Julia
- Stars
- 55
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Starting a discussion to cleanly specify a Julia message. This will help in
- swappable transports at a "message" level. For example, 0MQ or MPI. See https://github.com/JuliaParallel/MPI.jl/issues/60
- messages that can be routed via intermediate nodes - important when we support other topologies.
- implementation of reliable/guaranteed message delivery system
- user defined messages - the subsystem should be able to transport and hand-off user defined message for processing by user code.
- recovery from errors while deserializing messages. Well defined message boundaries should help.
A Julia message header could include
- version
- from_pid
- to_pid
- length in bytes
- message_name - symbol used to identify the handler
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.