Re: [usocket-devel] [drakma-devel] [patch] Resubmit drakma timeout for sbcl.
Hi Edi, 2011/3/26 Edi Weitz <edi@weitz.de>:
On Sat, Mar 26, 2011 at 6:17 PM, Александр Литвинов <lan@academsoft.ru> wrote:
There was the same decision at Dec 2007. Now, three years later, you have not changed it.
Well, I don't think it's too bad not to change your mind every year... :)
Actually, I had hoped that there had been some development in usocket since.
Well, there has been some development in usocket in the direction of supporting timeouts. On platforms where timeouts are not supported, an UNSUPPORTED-FEATURE condition is signalled. If that's ignored, everything should just continue without the timeout settings. If the above is not good enough, could you indicate what more needs to happen to make it so? Bye, Erik.
Hi, Erik Could you tell me what exact timeout feature they want? Setting Read/Write timeout when doing SOCKET-CONNECT? or Apply new timeout values to exist usocket object? --binghe 在 2011-3-27，03:11， Erik Huelsmann 写道：
Hi Edi,
2011/3/26 Edi Weitz <edi@weitz.de>:
On Sat, Mar 26, 2011 at 6:17 PM, Александр Литвинов <lan@academsoft.ru> wrote:
There was the same decision at Dec 2007. Now, three years later, you have not changed it.
Well, I don't think it's too bad not to change your mind every year... :)
Actually, I had hoped that there had been some development in usocket since.
Well, there has been some development in usocket in the direction of supporting timeouts. On platforms where timeouts are not supported, an UNSUPPORTED-FEATURE condition is signalled. If that's ignored, everything should just continue without the timeout settings.
If the above is not good enough, could you indicate what more needs to happen to make it so?
Bye,
Erik.
Hi Chun, 2011/3/27 Chun Tian (binghe) <binghe.lisp@gmail.com>:
Hi, Erik
Could you tell me what exact timeout feature they want? Setting Read/Write timeout when doing SOCKET-CONNECT? or Apply new timeout values to exist usocket object?
As far as I understand, the request is to for SOCKET-CONNECT to be cancelled after a certain timeout period expires. I don't think that's a read/write timeout, but rather a way to limit the waiting time until a valid connection is established. Bye, Erik.
在 2011-3-27，03:11， Erik Huelsmann 写道：
Hi Edi,
2011/3/26 Edi Weitz <edi@weitz.de>:
On Sat, Mar 26, 2011 at 6:17 PM, Александр Литвинов <lan@academsoft.ru> wrote:
There was the same decision at Dec 2007. Now, three years later, you have not changed it.
Well, I don't think it's too bad not to change your mind every year... :)
Actually, I had hoped that there had been some development in usocket since.
Well, there has been some development in usocket in the direction of supporting timeouts. On platforms where timeouts are not supported, an UNSUPPORTED-FEATURE condition is signalled. If that's ignored, everything should just continue without the timeout settings.
If the above is not good enough, could you indicate what more needs to happen to make it so?
Bye,
Erik.
participants (2)
-
Chun Tian (binghe) -
Erik Huelsmann