寄件者: live-devel-boun...@ns.live555.com [live-devel-boun...@ns.live555.com] 代表
Ross Finlayson [finlay...@live555.com]
寄件日期: Thursday, 9 September, 2010 3:33
收件者: LIVE555 Streaming Media - development & use
主旨: Re: [Live-devel] Graceful handling of socket error
>To answ
To answer your earlier question, I get error code 10038 on Windows
This is "ENOTSOCK", which indicates that one of the sockets specified
in the "select()" call was not actually a socket - either because it
had not actually been created, or because it had already been closed.
This indicates a
寄件者: live-devel-boun...@ns.live555.com [live-devel-boun...@ns.live555.com] 代表
Ross Finlayson [finlay...@live555.com]
寄件日期: Wednesday, 8 September, 2010 19:43
收件者: LIVE555 Streaming Media - development & use
主旨: Re: [Live-devel] Graceful handling of socket error
I pr
I pretty much agree with this. What I'll probably do (in some future
release) is change the calls to "abort()" to some new virtual
function (of the "UsageEnvironment" class) called "internalError()"
(or something). The default implementation of this might still be to
call "abort()", but devel
On Wed, Sep 8, 2010 at 2:58 PM, Ross Finlayson wrote:
> I am suggesting the call to abort() in the function
> BasicTaskScheduler::SingleStep() at line 95 in BasicTaskScheduler.cpp to be
> replace with something that is less destructive (C++ exception?) since a
> socket error can happen for legiti
I am suggesting the call to abort() in the function
BasicTaskScheduler::SingleStep() at line 95 in
BasicTaskScheduler.cpp to be replace with something that is less
destructive (C++ exception?) since a socket error can happen for
legitimate reasons (remote closed, ...).
Perhaps, although my in
Hello,
I am suggesting the call to abort() in the function
BasicTaskScheduler::SingleStep() at line 95 in BasicTaskScheduler.cpp to be
replace with something that is less destructive (C++ exception?) since a socket
error can happen for legitimate reasons (remote closed, ...).
Regards,
John Tam
