On 5 May 2012 17:00, Eliot Miranda <[email protected]> wrote: > > > On Fri, May 4, 2012 at 6:23 PM, Igor Stasenko <[email protected]> wrote: >> >> Hi, David, all >> >> i just want to know, if we can use FFI calls, for implementing an >> OSProcessPlugin functionality (or at least most of it). >> and if there parts which is hard to implement, i would like to know >> what and why. > > > Once we have the threaded FFI and the threaded VM then yes, because one can > block one thread in a read without blocking the entire VM. But without the > threaded VM one needs asynchronous i/o.
It's mildly off-topic, but I was under the impression that asynchronous i/o beat the trousers off blocking i/o, specifically when one has hundreds/thousands of sockets to process. So while it might be _nice_ to have blocking i/o as an option (one can often write clearer code), it's not something that (at least AFAIK) scales very well. frank >> If you want to ask, why one would want to do this.. the answer is simple: >> we stated previously, that we want to reduce the VM complexity by >> implementing things at language side, when it possible, >> leaving only key parts to VM. >> This is the main reason why i consider implementing OSProcess using >> purely FFI, not because of quality of OSProcessPlugin >> implementation etc. >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > best, > Eliot >
