do you think www.aws.org runs on aws?
For those inter st in the finest writing of all time https://www-allure-com.cdn.ampproject.org/v/s/www.allure.com/story/best-sex-tip-by-zodiac-sign/amp?amp_gsa=1&_js_v=a6&usqp=mq331AQKKAFQArABIIACAw%3D%3D#amp_tf=From%20%251%24s&aoh=16392879347932&referrer=https%3A%2F%2Fwww.google.com&share=https%3A%2F%2Fwww.allure.com%2Fstory%2Fbest-sex-tip-by-zodiac-sign
What it is What it is not Supported Implementations Examples Documentation Getting it Extensions Reporting Bugs Mailing Lists What is happening ASDF is the de facto standard build facility for Common Lisp. Your Lisp implementation probably contains a copy of ASDF, which you can load using (require "asdf") . ASDF 3 is the current successor to Daniel Barlow's ASDF. It was rewritten for improved portability, robustness, usability, extensibility, configurability, internal consistency, and the ability to deliver standalone executables. Its notable versions include pre-release 2.27 on February 1st 2013, first stable release 3.0.1 on May 16th 2013, major releases 3.1.2 on May 6th 2014, 3.2.0 on January 10th 2017 and 3.3.0 on October 6th 2017. The latest release is 3.3.1, publish...
and https://github.com/robert-strandh/CLIMatis
CL-PREVALENCE is an implementation of Object Prevalence for Common Lisp. It was written by and is being maintained by Sven Van Caekenberghe . CL-PREVALENCE is using S-XML for the XML serialization protocol (there is also a more Lisp-like s-expression-based serialization protocol). Object Prevalence is a simple but interesting concept first proposed by Klaus Wuestefeld in 2001. IBM developerWorks has a reasonable Introduction to Object Prevalence article. The main Java implementation is called Prevayler , with a (chaotic) wiki site with lots of information and discussions. The following academic paper seems to describe the most essential features of Object Prevalence, without naming it as such: A Simple and Efficient Implementation for Small Databases by Birrell, Jones, and Wobber [1987]. Basically, the idea is this: Most databases are only a couple o...
ChapterĀ 9 Interprocess Communication under LISP The REMOTE Package Connecting Servers and Clients Remote Evaluations Remote Objects The WIRE Package Untagged Data Tagged Data Making Your Own Wires Out-Of-Band Data by William Lott and Bill Chiles CMUCL offers a facility for interprocess communication (IPC) on top of using Unix system calls and the complications of that level of IPC. There is a simple remote-procedure-call (RPC) package build on top of TCP/IP sockets. 9.1 The REMOTE Package The remote package provides simple RPC facility including interfaces for creating servers, connecting to already existing servers, and calling functions in other Lisp processes. The routines for establishing a connection between two processes, create-request-server and connect-to-remote-server , return wire structures. A wire maintains the current state of a connection...
Protocol prev | up | next | toc Transactions prev | up | next | toc ( defclass transaction ( ) ( ) ) ( defgeneric perform ( transaction ) ( :documentation "Run TRANSACTION atomically with respect to all other threads in a new thread. If the transaction retries, then the thread loops again re-executing the transaction and commiting it to memory. PERFORM returns a thread created by BORDEAUX-THREADS as its value." ) ) ( defgeneric execute ( transaction ) ( :documentation "Execute TRANSACTION and return 3 values. 1. A boolean specifying whether or not the transaction retried. 2. A transaction log of all the changes that occured. 3. A list of values that TRANSACTION returns." ) ) ( defgeneric orelse ( tx1 tx2 ) ( :documentation "Compose two transactions alternatively. ORELSE returns a new transaction. We perform TX1 and if it succeeds then we're done. If it fails then we perf...