[admin] New project
Hello, I am currently working on a little (but ambitious) networking library, using code I had been writing in the past as well as new code. Since it might be useful to other people, I thought it would be a good idea to have it hosted on common-lisp.net, if the domain administrators agree on the usefulness of such a thing. Here are the details: Project name: unetwork Developer name: Matthieu Villeneuve License: LGPL Description: unetwork is a Common Lisp networking library. Its goal is to work on all CL implementations, and to support: - sockets (UDP, TCP) - address resolution - various protocols (HTTP, SMTP, POP, IMAP, NNTP, IRC,...) Status: Currently, only CMUCL is supported (tested). Support for SBCL is being added. Sockets and name resolution work. Basic operations work for HTTP, SMTP, POP, NNTP. Thanks, -- Matthieu Villeneuve
matthieu.villeneuve@free.fr writes:
Hello,
I am currently working on a little (but ambitious) networking library, using code I had been writing in the past as well as new code. Since it might be useful to other people, I thought it would be a good idea to have it hosted on common-lisp.net, if the domain administrators agree on the usefulness of such a thing. Here are the details:
Project name: unetwork
Developer name: Matthieu Villeneuve
License: LGPL
Description: unetwork is a Common Lisp networking library. Its goal is to work on all CL implementations, and to support: - sockets (UDP, TCP) - address resolution - various protocols (HTTP, SMTP, POP, IMAP, NNTP, IRC,...)
Status: Currently, only CMUCL is supported (tested). Support for SBCL is being added. Sockets and name resolution work. Basic operations work for HTTP, SMTP, POP, NNTP.
Cool! /me approves. Regards, Mario.
Project name: unetwork
Sounds very good! I approve. However, Have you considered using LLGPL instead of LGPL? http://opensource.franz.com/preamble.html LGPL is ok, but subject to interpretation when used with Lisp due to it's C-centric jargon. For example: is dumping a core static or dynamic linking? What about fasl-loading? Are new methods dispatching on the classes in the library work that uses the library, or work based on the library? Cheers, -- Nikodemus Siivola
Selon Nikodemus Siivola <tsiivola@cc.hut.fi>:
Project name: unetwork
Sounds very good! I approve.
However, Have you considered using LLGPL instead of LGPL?
http://opensource.franz.com/preamble.html
LGPL is ok, but subject to interpretation when used with Lisp due to it's C-centric jargon. For example: is dumping a core static or dynamic linking? What about fasl-loading? Are new methods dispatching on the classes in the library work that uses the library, or work based on the library?
I agree. I'll change the license to LLGPL. Thanks, -- Matthieu Villeneuve
participants (4)
-
Erik Enge -
Mario Mommer -
matthieu.villeneuve＠free.fr -
Nikodemus Siivola