Oh what shall I put here?
I really don’t know.
The has it all, I fear—
And there’s little else to show.
Still, if you’re curious, there's more about me…
Recent blog posts
Teepee design: the HTTP method
Now we come to the
Methodtype. While there are a few improvements to be made, this is one of the things that probably can’t be significantly improved on over rust-http.
Teepee design: header representation
Header representation is a critical matter to Teepee’s design: it is uncompromisingly strongly typed, but there must be tradeoffs. After trying quite a few different schemes at length, I have settled upon quite a novel scheme which I believe to optimally balance all considerations.
Status-Line, take two My first look at the
Status-Linekept largely to what rust-http had done; some great discussion came up and a conceptual flaw in my models was revealed. Now I present some better options.
Teepee design: a careful look at the HTTP/1.1
rust-http has a nice
Statusenum which provides good, strong typing of statuses, but alas, it is not without its issues. Let’s take a look at the
Status-Lineas it is defined.
Introducing Teepee: the next step for rust-http
rust-http was but an experiment, an essay in the craft. Here, at last, is the real thing: the Teepee project, a properly engineered HTTP toolkit.
Blindly random (or: old stories + computers = ?)
Have you ever wondered what the storytellers of yore would have done if computers had been in common usage? All of a sudden, people might start choosing supposedly random things scientifically…
Say “no” to import side‐effects in Python
When you write Python code, please make sure that you don’t have side‐effects in your module imports. It breaks things and makes people sad.
- See more blog posts…