On Sun, 09 Feb 2014 01:51:13 GMT, Kelet wrote:
I've thought about it a bit, and at least for the initial stages, I think I'm just going to create an interface for implementing backends for the task spawning system. I'll implement my own back ends: One synchronous, one using function pointers/delegates plainly, one using fibers, and one using vibe-d. I'm unsure if for the non vibe-d backends whether it is worth using libevent for UDP, though. It seems like it is much more useful for things like TCP or monitoring files.
Why would you create multiple backends ?
I'd say prototype it in vibe.d and if it is not fast enough profile it, fix it and send pull requests to vibe.d ....
That way everybody useing vibe.d can be as fast as you