March 30th, 2011
“+1” is a convention that arose on the Apache Software Foundation mailing lists. The ASF still has the best, most functional process for mailing list based collaboration which has ever been evolved of which -1/0/+1 is only the thin wedge. (the whole vocabulary of
commit-then-review, etc is incredibly important when trying to implement a diversity of tactics over email, as we ran into time and time again with Indymedia). Worth exploring their process in depth.
Anyway, Google launched a “+1” product today, and there was some discussion as to where the “+1” convention came from. The first place I ever encountered it was this email from Rob Hartill, on Wed, 15 Mar 1995, as part of one of the early patch voting rounds on Apache 0.7.x (the Apache foundation having formed the previous month to turn NCSA httpd into Apache).
I'll use a vote of
-1 have a problem with it
0 haven't tested it yet (failed to understand it or whatever)
+1 tried it, liked it, have no problem with it.
Rob might have adapted it from an earlier source, but I’ve never seen it.
October 28th, 2005
One of my key goals when moving Laughing Meme over to Typo was not to break the nearly 4 years of accumulated URLs. This involved some tweaking of Typo’s importer script to maintain my old
ids1, and some routes tweaking. So far so good.
But what about the pieces of the site not maintained by MT, pieces that expect to be handled by Apache, not dispatch.fcgi? For that ProxyPass if you friend. It isn’t a sweeping solution, but as I bring pieces of the site online that use PHP, server side includes, or just DirectoryIndex, I’m using ProxyPass to re-route the URLs before they fall into the Rails’ event horizon. Works great.
1. Actually, was a bit more complicated them that, as I combined several MT blogs (LM, MLPs, Work, etc) into one, so I let the importer create a
id, but also hang onto the MT id in a new column
December 21st, 2004
Much concern, hand wringing and advice on RSS bandwidth issues lately. (see Regular Sucking Schedule, and HowTo RSS Feed State). Here’s some more.
skipHours (and co.), ttl, and mod_syndication are all considered harmful. They’re all under specified, highly ambiguous, poorly supported, poorly implemented, and move logic into the file which should be (and is) in the protocol. Rule of thumb, if your bandwidth saving mechanism is in your feed, it’s a mistake. They promise false hopes of salvation, ignore them.
HTTP Will Save You
Rather look to:
- Conditional GET, learn it, live it, love it. Trivial to support, you have my permission to ban clients which don’t support it.
- GZIP encoding, the obvious solution to bandwidth concerns is to swap a little CPU (and the magic of HTTP caching really does minimize it), for a whole lot of bandwidth savings. Been looking for a reason to upgrade to Apache 2.0? How about moddeflate is included by default and is more stable then the arcane (and nomadic) modgzip (which was a beacon a in the darkness in its day)
- RFC 3229 aka HTTP deltas, and modspeedyfeed (reason #2 for upgrading Apache 2.0). Wave of the future, next puncture in the equilibrium, Sam has some notes: Varg ETag, Syndication with RFC3229, RFC3229 enabled, modspeedyfeed.
It’s All About Apache2 and HTTP/1.1
This post also does double duty as the my weighing in on Apache2 vs PHP mini- controversy
Obviously none of this will save you from the bandwidth concern of podcasting (or videoblogging!). I’m willing concede that those concerns are beyond the scope of basic HTTP, and point your attention to BitTorrent
February 26th, 2004
I started out tonight to install a parallel Apache2 (2.0.48) and PHP5 (5.0.0b4) on the laptop, to complement the existing Apache/PHP4 install. And I thought I would keep notes as I did it, maybe turn it into an extended blog entry, “Man Conquerors Technology” and all that, you know the type. Who knows, if it really got hairy, maybe I could make into an article for O’reilly. My scholarly ambitions were foiled once again; the software was just too damn easy to install
> ./configure --enable-mods-shared=ALL
> make install
Then tweak the conf file a bit. UserDirs should be set to Sites for example. Probably want to set User/Group to www/www. Also note that Port has been totally superceeded by Listen.
> apt-get install libxml2
> ./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql=/usr/local/mysql --with-libxml-dir=/sw --prefix=/usr/local/php5
> make install
I first had to upgrade my libxml2, which Fink did smoothly. Then configure wasn’t looking in /sw for my libraries, and rather then figure out why I told it explicitly where to find libxml. I installed into the prefix /usr/local/php5 in order not to step on the toes of my PHP4 install. This is especially useful as I’m finding a number of PEAR module need to be patched to run under PHP5, so I need separate PEAR directories for v4 and v5
So now I’ve got Apache/1.3.29 PHP/4.3.4 (entropy) responding on port 80, and Apache/2.0.48 PHP/5.0.0b4 responding on port 81.
Oh, and Magpie works just fine under PHP5.