Hi Wim! On Mon, Nov 7, 2016 at 7:05 AM, Wim Dumon <w...@emweb.be> wrote: > Hey Frank, > > After reviewing the documentation, I have to admit your remark is correct: > the documentation is confusing. > > In reality, most errors will be reported by throwing exceptions. > > If the server was already running, start() will return false, and (for > wthttp) if the server does not have to be stopped because Wt was compiled > without thread support (and the server will thus execute in the context of > the main thread), start() will also return false.
Okay, that makes sense. > I believe we should document the return value of start() as indication of > the need of calling stop(): if start() returns true, the server has to be > stopped by calling stop(). If start() returns false, no extra instance of > the server is running. Thanks for clearing all that up for me. (It also makes clear to me what was going on in some of the sample code I was looking at.) > I'm not sure if all connectors correctly implement > this behaviour at this point, though. > > Best regards, > Wim. Thanks. K. Frank > On 3 November 2016 at 22:55, K. Frank <kfrank2...@gmail.com> wrote: >> >> Hello List! >> >> Does WServer::start() ever return false, or does it always signal >> error conditions by throwing exceptions? >> ... ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
