4 posts filed under http.
The MongrelDB PHP client maps HTTP status codes to a small typed exception hierarchy, so a 401 is an AuthException, a 409 is a ConstraintException carrying the server's error code and the failing operation index, and your catch blocks read like the failure modes they handle.
A walk through the actual HTTP surface mongreldb-server exposes, from /sql and /txn to sessions, pagination cursors, and the /kit/* typed routes, and why plain HTTP was the right transport bet.
MongrelDB runs in-process or behind mongreldb-server, keeping one storage and query engine while changing ownership, authentication, serialization, and resource boundaries.
MongrelDB supports 35 languages through nine embedded native bindings and 26 language-native HTTP clients, with one engine contract under both boundaries.
