Is it correct that sendMail is blocking ? Or do I do something wrong ?
I am using the code from the sendMail example and basically call it once a HTTP request comes in but this gets blocked by the mail sending and times out I think ( at least CoreFiberTask spits an Access Vio ).
And if I wrap the code in a runTask(..) call all works out fine..
On 2013-11-10 13:41:00 +0000, Stephan Dilly said:
Is it correct that sendMail is blocking ? Or do I do something wrong ?
I am using the code from the sendMail example and basically call it
once a HTTP request comes in but this gets blocked by the mail sending
and times out I think ( at least CoreFiberTask spits an Access Vio ).And if I wrap the code in a runTask(..) call all works out fine..
AFAIK, All IO in vibe-d appears blocking from the calling fiber.
However, control is actually passed back to the event loop during that
time.
On Sun, 10 Nov 2013 11:04:11 -0500, Shammah Chancellor wrote:
On 2013-11-10 13:41:00 +0000, Stephan Dilly said:
Is it correct that sendMail is blocking ? Or do I do something wrong ?
I am using the code from the sendMail example and basically call it
once a HTTP request comes in but this gets blocked by the mail sending
and times out I think ( at least CoreFiberTask spits an Access Vio ).And if I wrap the code in a runTask(..) call all works out fine..
AFAIK, All IO in vibe-d appears blocking from the calling fiber.
However, control is actually passed back to the event loop during that
time.
Yeah you are right... Hard to get my head around sometimes. Nodejs ruined me :)
But in the end this fiber way of things is much simpler to read.
