Re: vibe.d with explicit threads/threadpool instead of fibers
On Tuesday, 25 October 2016 at 21:23:21 UTC, Arun Chandrasekaran wrote: I am looking for a RESTful framework in D, which can interact with an existing backend processes (C++) via ZeroMQ and shared memory. I thought vibe.d might be a viable option. But I discussed with someone on Freenode #d and found that vibe.d doesn't support explicit threading [1]. I looked at vibe.d examples, one of them uses futures [1], which implies explicit thread handling is possible. But I'm not sure about pre-spawned threadpool. [1] https://github.com/rejectedsoftware/vibe.d/blob/master/examples/future/source/app.d
vibe.d with explicit threads/threadpool instead of fibers
I am looking for a RESTful framework in D, which can interact with an existing backend processes (C++) via ZeroMQ and shared memory. I thought vibe.d might be a viable option. But I discussed with someone on Freenode #d and found that vibe.d doesn't support explicit threading [1]. Can someone confirm the behaviour? Is it not possible to allocate a bunch of threads or a threadpool for vibe.d to work with? PS: We have this working already with C++ only solution where the frontend communication happens on protobuf over ZeroMQ. I'm just trying to migrate it to RESTful interface. [1] http://pastebin.com/cAw2yaYg
