Question 1

How does Dexador compare to Drakma for Common Lisp HTTP clients?

Accepted Answer

Dexador is faster due to connection pooling and has cleaner APIs, but Drakma is more mature and stable, as Dexador is still in beta with potential API changes. Benchmarks show Dexador can be nearly twice as fast for repeated requests.

Question 2

How to handle errors and retry failed requests in Dexador?

Accepted Answer

Use the `http-request-failed` condition with handlers like `dex:ignore-and-continue` or `dex:retry-request` for structured error management. For example, you can bind handlers to retry up to 5 times with intervals.

Question 3

Does Dexador support SOCKS5 proxies on Windows?

Accepted Answer

No, the README states that proxy support, including SOCKS5, is not available on Windows backends, which limits functionality for Windows users needing proxy configurations.

Question 4

Is Dexador production ready or still in development?

Accepted Answer

It's marked as beta quality with likely API changes, so it's not recommended for production systems that require stability. Use it for experimental or non-critical projects instead.

Question 5

How to upload files using Dexador in Common Lisp?

Accepted Answer

Include a pathname in the `:content` alist when making a POST request, and Dexador will automatically detect and send it as multipart/form-data, as shown in the example with photo uploads.

Question 6

What are the performance benefits of Dexador's connection pooling?

Accepted Answer

Connection pooling skips TCP handshakes for repeated requests to the same host, significantly improving speed. Benchmarks show it reduces real-time execution by about half compared to Drakma for 30 requests.

Dexador

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Open Source Alternative To

Frequently Asked Questions