Re: fork/waitpid and std.concurrency.spawn
FreeSlave via Digitalmars-d-learn Wed, 23 Jul 2014 02:12:32 -0700
Seems like you need inter process communication. There are many
ways to make one. For example, through sockets. You may use D
bindings to ZMQ or other library, or just use std.socket.
Anyway the process will be represented by the whole program, not
just one function as in case of thread.
- fork/waitpid and std.concurrency.spawn Puming via Digitalmars-d-learn
- Re: fork/waitpid and std.concurrenc... FreeSlave via Digitalmars-d-learn
- Re: fork/waitpid and std.concur... Puming via Digitalmars-d-learn
- Re: fork/waitpid and std.co... FreeSlave via Digitalmars-d-learn
- Re: fork/waitpid and st... Puming via Digitalmars-d-learn
- Re: fork/waitpid a... FreeSlave via Digitalmars-d-learn
- Re: fork/waitp... FreeSlave via Digitalmars-d-learn
- Re: fork/waitp... Puming via Digitalmars-d-learn