Please update usocket - needed for the (already updated) drakma

[avodonosov]

The recent drakma version (already included into the February quicklisp) passes new value to the :nodelay argument of usocket:socket-connect. This value is supported only by the recent usocket (not included into quicklisp yet).

[quicklisp]

On what platform is this an issue? I can't reproduce with SBCL on OS X.

[avodonosov]

13.02.2012, 02:57, "Zach Beane" reply@reply.github.com:

On what platform is this an issue? I can't reproduce with SBCL on OS X.

On CLISP for example.

Some more info.

In the previous version of usocket, the socket-connect function already has
the :nodelay parameter, but with only two possible values: T or NIL.

Drakma specified :nodelay T. On the Lisps where nodelay was not
possible, usocket signalled error "Nodelay unsupporeted".

Now we added :nodelay :if-supported. With that value usocket sets the nodelay mode
for sockets if it can; but if it can not the error is not signalled. Drakma switched
to :nodelay :if-supported, which allows it to work on all lisps.

In the last QL distro we have new drakma but old usocket. I.e. drakma passes
the :nodelay :if-supported to the usocket which doesn't know this value.
It may be the case (I don't know for sure and it will vary on different Lisps)
that :if-supported has the same effect as T.

If so, the current QL is not worse than the previous one: some lisps have working
drakma, other lisps like CLISP, CMUCL and SCL have broken drakma.

But with new usocket these lisps will also have working drakma.

Therefore the update is desirable.

[quicklisp]

I don't show any newer releases of usocket. Is it only updated in git?

[avodonosov]

13.02.2012, 03:52, "Zach Beane" reply@reply.github.com:

I don't show any newer releases of usocket. Is it only updated in git?

In SVN to be more precise.

[quicklisp]

I recommend encouraging usocket developers to make a new release in time for next month's update.

In the meantime, people affected by this update should go back to the previous dist.

[avodonosov]

Ok. I reported this to the usocket-devel

[quicklisp]

The next dist update will include the new usocket.