On 4/15/08, Hans Hübner hans@huebner.org wrote:
Erik,
I am currently porting Hunchentoot to usocket and there I noticed that no API is provided to set timeouts either. I will work on adding those and also extend the argument list for all implementations. I will be sending a patch later this week.
That's right. I have your patch in my working copy regarding addition of TIMEOUTs, but if you're going to do more work on it, I'll hold. The reason it was not committed yet was my question regarding deadlines (and the fact that I was busy yesterday evening - blocking a commit).
Bye,
Erik.
-Hans
On Fri, Apr 11, 2008 at 11:41 PM, Erik Huelsmann ehuels@gmail.com wrote:
since I last posted my patch, I have made some more changes to usocket to support connect timeouts. I also removed the need for platform specific syscalls files - Gary Byers suggested that we use #_select instead of the direct syscall interface, which I think is the right thing to do.
Let me know if that suits.
It suits. I committed most of the patch as a series of unrelated commits, because that will let me backport some of the changes independently to the release branches.
The only part I did not commit (yet) was the one which introduced the timeouts for SOCKET-CONNECT: I found you introduced 2 keyword parameters on some implementations, but only one for others. Next to that, I'm unclear on what the difference is between the two: could you (shortly) explain the difference between TIMEOUT and DEADLINE?
Thanks in advance!
Bye,
Erik.
http://bknr.net/trac/changeset/2795?format=diff&new=2795
It fixes loading of system calls for Linux and FreeBSD. I have opened a bug with Clozure to make them move to a unified system call loading interface so that applications do not need to dispatch on an architecture symbol, but until that went into CCL, the fix should be fine.
I missed this patch. I'll commit it tonight and backport it to the release branches it applies to.
Bye,
Erik.