Well, it finally happened. I caved. I bought Internets everywhere with a Sprint plan and the Novatel USB727 doohickey. Bonus points to Novatel for packing a GPS and a EVDO rev A modem into such a small package and providing working Linux instructions involving only standard kernel serial drivers!
My critique of the instructions is also a […]
http://forums.mysql.com/read.php?92,133026,133102
Hi. Since the updates on a memory table should be very fast, the locks are taken for a very short time only. I won’t expect that they become a bottleneck. But I must admit that I don’t have any experiences with applications like this. If they do indeed become a bottleneck, you could try […]
Grey is so out! Blue? Green? Hmm, how’s brown these days?
Here we go…
Done! Edit draft-ietf-ipv6-ra-flags-option-02 and draft-weiler-dnssec-dlv-04
Done! Submit draft-ietf-sieve-refuse-reject-05
Done! Release libSieve 2.2.6
Update docs
New callbacks for address and header parser errors
Saw Raw & Uncut Festival and Balkan Beat Box on Saturday evening. Hurrah for fun!
A few things to do before I get to libSieve 2.2.6…
More checkins.
Bracketed comments.
Stress tests for header and address parsers.
Resolve extant memory leaks (switch to a memory pool system? methinks yes).
Benchmark parsing a monster script. Compare with previous versions.
Stress test the stack with deeply nested if blocks.
Someone else proves that they can take even longer on something even simpler: KDE Bug 122870. In a nutshell:
Opened: 2006-03-01 00:32
Gist of fix required: accept “{” bytecount “+}” in addition to “{” bytecount “}” for RFC compliance.
Closed: 2007-08-06 19:29
Thanks nonetheless to the KDE folks for closing this bug; fewer complaints from my DBMail users!
This week’s Two Small Farms CSA basket came with this weird thing: Well, what to do? Cut it up and saute it in olive oil with some garlic! Yum
Today I spent some time hacking on libSieve for the first time in way too long. I was telling a friend about the inefficiency of putting all of your keywords into a lexer because it has to go through tons of state shifts to get to the terminals. A better way to do it is […]
Why is calendaring still such a pain in the ass? There’s been nothing but a proliferation of propriety solutions, web apps that store their data locally and do not share it, servers that speak antiquated versions of dodgy protocols, and clients that are continually being rebuilt from the ground up instead of evolved to be […]
This is a crosspost. Let’s see if it works…
This is more stuff. It should be an lj-cut that links back to my blog. Wow cool if it works!