Il giorno 25/ott/2016, alle ore 23:22, Anton Vodonosov avodonosov@yandex.ru ha scritto:

Congrats!

Thanks!

26.10.2016, 00:20, "Chun Tian (binghe)" binghe.lisp@gmail.com:

...

Separated USOCKET and USOCKET-SERVER systems (only the server part depends on Portable-threads)

Does it mean some public function which were previously present in the USOCKET system now are unavailable until you load USOCKE-SERVER?

That’s true, but actually only the following three API symbols are not present if you don’t load USOCKET-SERVER system:

* The function USOCKET:SOCKET-SERVER (together with all underlying internal helper functions in server.lisp) * The special variable USOCKET:*REMOTE-HOST* * The special variable USOCKET:*REMOTE-PORT*

And of course the Portable-threads package won’t be loaded too. Noticed that SOCKET-SERVER is just a quick way to create trivial TCP and UDP servers. Serious users can still create their own TCP or UDP server using just the USOCKET package. I think almost all Quicklisp packages which depends on usocket are not affected by this change.

Regards,

Chun Tian (binghe)

Sorry, all my faults... They’re exactly the two packages that should depend on the new usocket-server system. And I should really export all symbols in the main usocket package (even some of them are not defined).

I have uploaded usocket-0.7.0.1 to the usual publication URL [1] with all known issues fixed. The “snmp-server” package now loads correctly even without modifications, but it won’t run correctly. I’ll make a new bugfix release of cl-net-snmp tomorrow.

Regards,

Chun Tian

[1] https://common-lisp.net/project/usocket/releases/usocket-latest.tar.gz

Il giorno 26/ott/2016, alle ore 17:28, Zach Beane xach@xach.com ha scritto:

I get an error in the USOCKET-TEST system that "SOCKET-SERVER" is not in the usocket package.

The SNMP-SERVER system also no longer builds.

http://report.quicklisp.org/2016-10-26/failure-report/snmp.html#snmp-server http://report.quicklisp.org/2016-10-26/failure-report/usocket.html#usocket-t...

Zach

On Tue, Oct 25, 2016 at 5:18 PM, Chun Tian (binghe) binghe.lisp@gmail.com wrote: Hi Common Lispers,

I’m glad to release usocket-0.7.0, a new major release.

Starting from this version, we have made two systems “usocket” and “usocket-server” separated, the purpose is to minimize package dependencies and loaded code. Previously we have some vendor code borrowed from “split-sequence” and “portable-threads” package, now these duplicated code were removed. Instead, we directly depend on the original package. (portable-threads [1] is only needed by usocket-server and usocket-test).

The LispWorks support has been carefully checked and confirmed working on version 4.4.x, 5.x, 6.x and 7.0.

There’s no new API symbols in this release. However, (few) people who is using SOCKET-SERVER API, please change the dependency from “usocket" to “usocket-server”. (sorry for this change)

Changes in 0.7.0:

• General: Separated USOCKET and USOCKET-SERVER systems (only the server part depends on Portable-threads)
• General: USOCKET (the client part) now depends on SPLIT-SEQUENCE (the exactly same vendor code is removed from usocket code base)
• New feature: [LW] (SOCKET-OPTION :TCP-NODELAY) and its SETF version now works on LispWorks 4/5/6/7.
• New feature: [LW] SOCKET-CONNECT now supports setting "tcp_nodelay" in version 4.x and 5.0.
• Bugfix: [CCL] fixed issues in SOCKET-SHUTDOWN
• Bugfix: [CLISP] fixed issues in WAIT-FOR-INPUT (Thanks to a patch by @vibs29, #27)
• Bugfix: [LW] fixed loading in version <= 6.0 (actually 0.6.5 only fixed loading in LW 6.1)
• Bugfix: [ECL] all compilation warnings were checked and fixed.

As usual, if you want to download this release, please check

    http://common-lisp.net/project/usocket/releases/

or just wait for next Quicklisp monthly dist updates. (or make a Git clone to usocket “master”, URL is given below)

The API documentation page was here:

    http://common-lisp.net/project/usocket/api-docs.shtml

Any feedback - bugs or hugs - will be greatly appreciated. Anyone is welcome to send pull request to our Git repository:

    https://github.com/usocket/usocket.git

Some future directions:

• More features in SOCKET-SERVER
• New IOlib backend!
• Add support for MKCL (this will be the 13th CL platform that we support)

Regards,

Chun Tian (binghe) USOCKET Team

[1] Now Quicklisp starts to use my version at https://github.com/binghe/portable-threads