Question 1

Is QURI faster than PURI for parsing URIs?

Accepted Answer

Yes, benchmarks show QURI parses URIs 6.6 times faster than PURI, as demonstrated in the README with 100,000 iterations taking 0.064s vs. 0.423s.

Question 2

How to handle query parameters with QURI?

Accepted Answer

Use the `uri-query-params` method for HTTP/HTTPS URIs to get or set an association list, and `url-encode-params` for encoding parameters into a form-urlencoded string.

Question 3

Does QURI support UTF-8 characters in URIs?

Accepted Answer

Yes, QURI correctly handles UTF-8 characters, with functions like `url-decode` decoding percent-encoded strings into Unicode, as shown in the example with Japanese characters.

Question 4

What are the main differences between QURI and Hunchentoot for URL encoding?

Accepted Answer

QURI is 3.8 times faster for URL encoding than Hunchentoot and doesn't implicitly encode/decode, giving more control but requiring manual handling compared to Hunchentoot's built-in web server utilities.

Question 5

How to install QURI in a Common Lisp project?

Accepted Answer

Install via Quicklisp by running `(ql:quickload :quri)` or clone the GitHub repository. The README provides basic setup instructions but assumes familiarity with Common Lisp tools.

Question 6

Can QURI parse byte vectors instead of strings?

Accepted Answer

Yes, QURI accepts both strings and byte vectors as input for parsing, with optional start and end indices, offering flexibility for low-level or performance-sensitive code.

Question 7

What should I watch out for when migrating from PURI to QURI?

Accepted Answer

Key issues include the lack of implicit encoding/decoding, changes in query value handling (e.g., numbers require explicit conversion), and potential breaking changes in version upgrades, as noted in the change log.

quri

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Found a gem we're missing?

Cons

Open Source Alternative To

Frequently Asked Questions