add the ability to call custom code in scheduler dynamic context #7
Conversation
The idea behind that is to make it possible, to set the value of a fluid in the dynamic context of schedulers.
| (for-each (lambda (sched affinity) | ||
| (call-with-new-thread | ||
| (lambda () | ||
| (and thread-init (thread-init)) |
There was a problem hiding this comment.
This should probably go inside %run-fibers actuallly.
|
AFAIU what you need is a database connection, right? Why not make a non-fibers threadpool and communicate with that threadpool over channels? I don't think this patch will solve your problems as each fiber has its own dynamic state. The dynamic state of the thread running the scheduler actually isn't visible to the fibers that the schedulers run! |
bummer!
yes, but the interface is not a port.
Maybe I will think about it. |
The idea behind that is to make it possible, to set the value of a fluid
in the dynamic context of schedulers.