Implementation of RFC 2388
A Common Lisp Amazon S3 client interface package
cl-sasl is a client implementation of the Simple Authentication and Security Layer (SASL) networking protocol.Currently the PLAIN, DIGEST-MD5 and ANONYMOUS mechanisms are implemented.
It can be found at xn--9dbdkw.se/cl-sasl.html and github.com/legoscia/cl-sasl/.
RFC2229 client for Common Lisp.
The Open Sound Control protocol, aka OSC
Protocol and framework for building parse results and other object graphs.
A simple iterator protocol for Common Lisp.
Simple protocol implementation for Common Lisp inspired by clojure.
The independent protocol part of Lichat.
A low-level Swank client.
A library for accessing octet-addressed blocks of data in big- and little-endian orders
Ivan Shvedunov, David LichteblauLicense:
common-lisp.netproject/plexippus-xpath/Download (tarball): Yes, see belowDownload (darcs get): http://www.common-lisp.net/project/plexippus-xpath/darcs/plexippus-xpath/
(darcsweb)This project is asdf-installable (release tarball) and available in clbuild (git version).
An implementation of XPath 1.0.
Feature overviewPlexippus XPath is an implementation of XPath 1.0, written entirely in
Implements XPath 1.0 (passes XSLT 1.0 test suite)
Supports any document model using an extensible CLOS protocol
Protocol implementations for STP and DOM built in
XPath functions and variables implementable in Common Lisp
Convert floating point values to IEEE 754 binary representation
Utilities for sending messages to Growl on Mac OS X.
Common Lisp interface to the IRC protocol
A library for handling netstrings as described in http://cr.yp.to/proto/netstrings.txt.
Common Lisp OAuth implementation
Perl compatible binary pack() and unpack() library
Common Lisp Erlang Interface - An implementation of the Erlang distribution protocol.
An implementation of the X Window System protocol in Lisp.
FirePHP debug utility
WebSockets for Hunchentoot
manardb: Fast, persistent, mmap'd Lisp object store Manardb provides persistent classes (integrated into the object system via the meta-object protocol), stored efficiently in memory mapped regions. It features transactions, two different garbage collection mechanisms (to clean up unreferenced objects in the database), in-place modification of arrays, efficient in-place numeric typed slots, and the ability to transparently serialise Lisp objects of many types (lists, vectors, floats, integers, symbols, strings).It allows Common Lisp programs to efficiently access in-memory representations of large numbers of persistent objects without putting pressure on the Lisp garbage collector.Homepage
mel-base is a library for handling email with support for Maildir, POP3, IMAP and SMTP folders.It makes no difference from the programmer's side if an E-Mail gets copied from a Maildir folder to an IMAP folder or from POP3 to Maildir. Sending E-Mails through SMTP is simply done through the same mechanism. One just copies an E-Mail from a folder supporting the "receiver" protocol like IMAP, Maildir or POP3 to the SMTP folder which supports the "sender" protocol.E-Mails are first-class objects and on-demand fetching of parts of an e-mail
like the header or a particular part is supported.Mel-base got used to implement a POP3 server, a Spam-Filter and a CLIM Mail-Reader/Composer (http://codeartist.org/mel/) and many small scripts to process, filter and deliver E-Mails. Mel-Base itself is Open Source and licensed under a license similar to the BSD License. The mentioned applications, while not Open Source, are available on request.Author: Jochen SchmidtIt works in SBCL , CMUCL, OpenMCL and LispWorks with partial support for
CLISP and ABCL. Porting it should be straightforward because implementation dependent parts are encapsulated in a thin compatibility layer.My fork policy:
I open sourced mel-base as a generic library for handling e-mails (and not just as base-library for mel) and I'm interested in getting feedback on how to enhance it further. I know that in the code-base of mel-base might be parts which may be useful for other purposes, but please think twice about it before creating unnecessary forks.If you have ideas, drop me an e-mail. If this really cannot hold you off; please use darcs to create a proper branch of the code-base so your work can get reused by users of mel-base. The darcs repository is at http://www.crispylogics.com/opensource/repos/mel-base/. Please don't just rip it off.To kire (Erik Enge): In #lisp you stated your intend to split mel-base into parts. Mel-Base already is quite modular in that each folder backend got implemented in its own ASDF module. I plan to go further on that road by factoring the backends out to different ASDF systems depending on mel-base as a core. If you still have those splitting plans - please contact me first.
-- Neonsquare (Jochen Schmidt), author of mel-base
Extensible object equivalence protocol
oAuth 1.0a server and client implementation, the successor to South.
PERCENT-ENCODING is an implementation of the URI encoding commonly used in internet protocols written by Max Rottenkolber.
Pg is a socket-level interface to the PostgreSQL object-relational Database.
Pg implements the client part of the frontend/backend
protocol, so does not require interfacing with the libpq library. SQL
types are converted to the equivalent Common Lisp types where
possible. Supports large objects (BLOBs).
Postmodern is a newer and much-much cleaner library. Its cl-postgres asdf system implements the same functionality as Pg -- Attila Lendvai
The only non portable code is the use of SOCKET-CONNECT. Versions are
provided for CMU Common Lisp (CMUCL), SBCL, OpenMCL, CLISP, LispWorks and Allegro Common Lisp (ACL). Corman CL doesn't support binary I/O on socket streams, so it doesn't work there.Pg is available under the GNU LGPL licence from www.chez.com/emarsden/downloads.
There are also Emacs Lisp and scsh versions of the library.This is a snapshot of the CVS repository at common-lisp.net/project/pg and it is not GPG signed.Here is the last released version, but it's quite old:http://www.chez.com/emarsden/downloads/pg-dot-lisp-0.19.tar.gzSample code:
(with-pg-connection (conn "testdb" "login" :host "dbhost" :password "secret")
(when (member "test_date" (pg-tables conn) :test #'string=)
(pg-exec conn "DROP TABLE test_date"))
(pg-exec conn "CREATE TABLE test_date(a timestamp, b abstime, c time, d date)")
(pg-exec conn "INSERT INTO test_date VALUES "
"(current_timestamp, 'now', 'now', 'now')")))
Stargreen Box Office uses Pg for its database glue layer; it's respectably fast, simple enough to see what it's doing, and impervious to PostgreSQL shared library versioning issues (because it doesn't use them). I'm very happy with it -- Daniel Barlow
You must set unix_socket_directory in your postgresql.conf to /var/run/postgresql
pg doesn't use the default path for the unix domain socket. See Socket Path.
A collection of basic utilities for syntactic
extension and basic data structure hadling,
developed over the years of CL history by efforts of different individuals,
and gathered under the unbrella of a hierarchy of packages
which can be used on-demand.
Common Lisp XML-RPC Package
Xmls is a small, simple, non-validating XML parser for Common Lisp. It's designed to be a self-contained, easily embedded parser that recognizes a useful subset of the XML spec. It provides a simple mapping from xml to lisp s-expressions and back.Features from the readme:
Free (BSD license).
Small and easily embedded. The entire parser is contained in one file and it's currently less than 500 lines of code. Xmls is written in pure lisp and requires no external parsing tools or foreign libraries.
Understands enough of the xml spec to parse many common documents, including those occurring in common internet protocols like xml-rpc, webdav, and BEEP.
Serializes s-expr list structures back to xml as well as parsing xml.
Parses and understands xml namespaces.
More information is available on the xmls homepage.XMLS has just been updated to version 1.4.1, fixing a bug in parsing CDATA.