[Documentation] Add simple example how to use Vibe.d timers

[ilya-stromberg]

See also http://forum.rejectedsoftware.com/groups/rejectedsoftware.vibed/thread/8516/

[s-ludwig]

Is the added unittest-example enough, or do you have something additional in mind?

[ilya-stromberg]

Thanks for unittest example. It's good as very simple example.

Can we add a little more complex example for sleep and setTimer in vibe.d/examples/timer folder?

[s-ludwig]

So what exactly are you after? Some kind of task interaction in a certain situation? I always looked at timers/sleep as something so simple that they are barely worth an example.

[ilya-stromberg]

OK. Have we got unittest for sleep function?

[s-ludwig]

I was seriously asking myself "WTF should an example for sleep show in addition to the obvious?". But there may be some value in showing how to specify the duration (e.g. 4.seconds()). Is that what you thought?

[etcimon]

I think it would be useful to have an example that shows how sleep doesn't block other tasks.

handler(HTTPServerRequest req, HTTPServerResponse res){
    import std.conv;
    runTask( { foreach ( i ; 0..5) sleep(1.seconds), res.write("sleep #1 seconds: " ~ i.to!string); });
    foreach ( i ; 0...5 ) sleep(3.seconds), res.write("sleep #2 seconds: " ~ (i*3).to!string);
}

[ilya-stromberg]

But there may be some value in showing how to specify the duration (e.g. 4.seconds()). Is that what you thought?

Yes, it is.

I think it would be useful to have an example that shows how sleep doesn't block other tasks.

Yes, it looks like a little more complex example that I wanted to see.

[s-ludwig]

I think it would be useful to have an example that shows how sleep doesn't block other tasks.

Yes, it looks like a little more complex example that I wanted to see.

But then I'd have to add examples for each and every blocking function, to show that it doesn't block other tasks. I don't know, maybe half a sentence about in the description is clear enough? But in general this is a basic concept of the whole library, so I don't think repeating it all over again for every function is a good idea.

[ilya-stromberg]

OK, OK. As I said, simple unittest should be enough.