At first, I just developed the prototype in the default GAE/J Eclipse environment until I could deliver a functional POC. After finding the GAE/J capabilities more than adequate for what we wanted to do, I was challenged to bring the project into our standard IntelliJ + Maven development environment. For the rest of this post, I’ll share a couple of tips and tricks for getting your GAE/J project to operate in this environment.

Basic POM File

There’s some funny business and frustration around the Maven community’s adoption of GAE/J, but I’ll skip that part of the story for right now. What I found is that the maven-gae-plugin project is the best place to go to for help Mavenizing a GAE/J build.

I have to say that it’s not ‘use the archetype’ easy (their archetype failed for me), but with a bit of elbow-grease and rummaging through their documentation I was able to get a decent and functional POM file built. Here it is (with some of our proprietary information scrubbed to protect innocent servers):

 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.widgetbox</groupId>
   <artifactId>image-proxy-webapp</artifactId>
   <version>1.0-SNAPSHOT</version>
   <name>Widgetbox :: Image-Proxy :: Webapp</name>
   <packaging>war</packaging>
   <properties>
     <gae.version>1.3.0</gae.version>
     <gae.app.name>qa-image-proxy</gae.app.name>
   </properties>
   <dependencies>
     <dependency>
       <groupId>javax.jdo</groupId>
       <artifactId>jdo2-api</artifactId>
       <version>2.3-eb</version>
       <exclusions>
         <exclusion>
           <groupId>javax.transaction</groupId>
           <artifactId>transaction-api</artifactId>
         </exclusion>
       </exclusions>
     </dependency>
     <dependency>
       <groupId>javax.transaction</groupId>
       <artifactId>jta</artifactId>
       <version>1.1</version>
     </dependency>
     <dependency>
       <groupId>com.google.appengine.orm</groupId>
       <artifactId>datanucleus-appengine</artifactId>
       <version>1.0.4.1</version>
     </dependency>
     <dependency>
       <groupId>org.datanucleus</groupId>
       <artifactId>datanucleus-core</artifactId>
       <version>1.1.5</version>
       <exclusions>
         <exclusion>
           <groupId>javax.transaction</groupId>
           <artifactId>transaction-api</artifactId>
         </exclusion>
       </exclusions>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>datanucleus-jpa</artifactId>
       <version>1.1.5</version>
       <scope>runtime</scope>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>geronimo-jpa_3.0_spec</artifactId>
       <version>1.1.1</version>
       <scope>runtime</scope>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>appengine-api-1.0-sdk</artifactId>
       <version>${gae.version}</version>
     </dependency>
   </dependencies>
   <build>
     <plugins>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-compiler-plugin</artifactId>
         <version>2.0.2</version>
         <configuration>
           <source>1.6</source>
           <target>1.6</target>
         </configuration>
       </plugin>
       <plugin>
         <groupId>net.kindleit</groupId>
         <artifactId>maven-gae-plugin</artifactId>
         <version>0.5.3</version>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-war-plugin</artifactId>
         <version>2.1-beta-1</version>
         <configuration>
           <filters>
             <filter>${project.build.directory}/version.properties</filter>
           </filters>
           <webResources>
             <resource>
               <directory>src/main/external</directory>
               <targetPath>WEB-INF</targetPath>
               <filtering>true</filtering>
             </resource>
           </webResources>
         </configuration>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-antrun-plugin</artifactId>
         <version>1.3</version>
         <executions>
           <execution>
             <phase>compile</phase>
             <configuration>
               <tasks>
                 <echo file="${project.build.directory}/version.properties">
                     friendlyversion=${project.version}
                 </echo>
                 <replace file="${project.build.directory}/version.properties" token="." value="-"/>
                 <replace file="${project.build.directory}/version.properties" token="SNAPSHOT" value="snapshot"/>
               </tasks>
             </configuration>
             <goals>
               <goal>run</goal>
             </goals>
           </execution>
         </executions>
       </plugin>
     </plugins>
   </build>
   <repositories>
     <repository>
       <id>maven-gae-plugin-repo</id>
       <name>maven-gae-plugin repository</name>
       <url>http://maven-gae-plugin.googlecode.com/svn/repository</url>
     </repository>
   </repositories>
   <pluginRepositories>
     <pluginRepository>
       <id>maven-gae-plugin-repo</id>
       <name>maven-gae-plugin repository</name>
       <url>http://maven-gae-plugin.googlecode.com/svn/repository</url>
     </pluginRepository>
   </pluginRepositories>
 </project>

(FYI, we’re not actively using any datastore functionality just yet, so if you are going to use this template please forgive me if those dependencies are a little bit wonky.)

Since Google hasn’t (yet) decided to publish their development environment in a Maven-friendly way, there’s a bit of dependency wonkiness involved in getting the maven-gae-plugin to work. I included the repository information required by the plugin (lines 121 – 134), but if you use a repository manager (like Nexus), you’ll want to remove those lines from the POM and add a proxy for the maven-gae-plugin’s repository.

To get the development environment working the plugin also requires access to the unzipped SDK as packaged by Google. The plugin tries to help you set this up (“gae:unpack”) but that failed for me. I was able to get stuff working by manually unzipping the SDK artifact downloaded directly from Google to the following directory:

~/.m2/repository/com/google/appengine/appengine-java-sdk/1.3.0/appengine-java-sdk-1.3.0

Incremental Improvments

Initially, I had kept the appengine-web.xml within the WEB-INF directory, but I realized I could make our Release Manager’s life a bit easier if I added a bit of build-time substitution.

Here’s our appengine-web.xml:

<?xml version="1.0" encoding="utf-8"?>
<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
	<application>${gae.app.name}</application>
	<version>${friendlyversion}</version>
	<system-properties>
		<property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/>
	</system-properties>
</appengine-web-app>

And you’ll see that I put it into a new source directory called ‘external’:

At build time, I use the AntRun plugin (lines 97-118) to create a small file under the target directory that holds a ’sanitized’ version of the standard Maven version. (I.e. “1.0-SNAPSHOT” becomes GAE-friendly “1-0-snapshot”.) I then use the Maven filter functionality available in the WAR plugin (lines 80-96) to copy the appengine-web.xml into its proper directory with the version substituted in.

You’ll also notice in our appengine-web.xml that we substitute in our application name. By default this comes from the properties section of the pom.xml file (line 11). I did this because we’ve actually got 2 different applications up on GAE’s servers, the QA version and the Production version. By default we build using the QA server’s application name, but when our Release Manager is building to upload to Production, all that is needed is an additional command-line argument of “-Dgae.app.name=<prod-name>”.

Running, Debugging, and Deploying

The two most valuable targets that maven-gae-plugin provide are “gae:run” and “gae:debug”. These will assemble your code in the standard Maven webapp target directories and run your app. (Note: “gae:debug” didn’t actually work for me until the 0.5.3 version of the plugin.)

There is also a “gae:deploy” target that is supposed to invoke the Google-supplied shell script that will upload your application to the Google servers, but it failed for me several time. Since then, I’ve defaulted to using the shell script directly to deploy my app once it has been built:

~/.m2/repository/com/google/appengine/appengine-java-sdk/1.3.0/appengine-java-sdk-1.3.0/bin/appcfg.sh \
    update \
    ./target/myApp-1.0-SNAPSHOT

Results

So, this is how we got up and running with GAE/J in our standard development environment. Hopefully this post ends up helping people out to reduce their bootstrap time when evaluating/investigating GAE/J for their own uses.

“The Anatomy of a Whale“: A nice write up on problem-finding and -solving within a large-scale operation.

X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.

I think this is a pretty cute and subtle way of looking for technically adept potential employees.

I’ve been starting to play with Google App Engine, both for personal projects and at work. Since most of my environments are Maven-based, I thought I’d go out and find a Maven Archetype or some kind of a POM file to bring these projects into my environment. I did find several blog posts trying to help: here, here, etc… The annoying thing you’ll notice on those blog posts is that Brian Fox ((formerly?) of Sonatype) posts a comment pointing towards Jason van Zyl’s post describing his efforts to Maven-ize the GAE SDK.

That would be all well and good if things had actually progressed. If you look at JvZ’s post, you’ll see he ends with “hopefully I’ll be able to get this out for Maven users by the end of the week!” What happens after that? Bupkis, nil, nothing, NADA!

There’s comments as late as Dec ‘09 expressing interest to use and/or help with the effort. But, there is NO RESPONSE from anyone at Sonatype.

I just find it galling that Sonatype would go on an all-out publicity spree talking people out of working on their own because JvZ himself was going to bring his skills to bear on the problem, only to completely fizzle out. I suspect the community at large would have been better off if those 4 or 5 early Maven + GAE adopters had continued on their own path, even if JvZ had succeeded.

Again: my patience with Maven/JvZ is waning. I’m eager to see what comes along next to take its place.

They gave me an electronic copy of the book to read, and asked for a 300 – 350 word review about the book. I’ve gotten it mostly to the point of ‘completion’, and any more changes would just fall under the category of ‘tinkering’.

Maven. I hate the word, as I hate hell, all Montagues, and MAKE.

Maven is a powerful Open Source build system which is becoming a de facto standard in Java development circles. Like any powerful tool, Maven has its own proponents and detractors, benefits and drawbacks. For example, one of the consistent issues that plagues the Maven ecosystem is a dearth of quality documentation.

When I heard about “Apache Maven 2 Effective Implementation”, I had hoped that it would be the One Book to rule them all, the One Book to find them, the One Book to bring them all and in the darkness bind them. Unfortunately, this is not that One Book.

“Apache Maven 2 Effective Implementation” is yet another effort by a Maven contributor to provide some clarity to Maven’s user community about how exactly to use Maven correctly. But much like the rest of the Maven documentation ecosystem, this book provides the type of documentation that only its author could love.

The author is obviously knowledgeable, however I can’t recommend this book as anything more than an incremental addition to the Maven user’s arsenal. Having been a Maven ‘believer’ since the late 1.x days, I would say that ALL the documentation I’ve seen on the subject has been no better than incremental. In most cases, like this one, the authors falls into a classical trap of technical documentation by explaining what to do, but rarely explaining why. (Nor, more importantly, explaining how to figure these things out for yourself).

I did find a few helpful tidbits of new information in the book. However, I’m not sure I would have been able to quickly find them again in a reference situation because the logical flow was all over the place. Example: Chapter 4 had ten pages of fundamental reporting information, which is great information to have; but maybe Chapter 5, which was titled “Reporting and Checks”, is where that information rightly should have resided.

Unlike some of the best technical books I’ve read, my ability to stay awake while reading this book was challenged because it is so very dry. I had no delusions of it being as compelling as the “Encyclopedia Galactica”, but the prose was completely wooden. This blandness and the previously mentioned problems render the book altogether forgettable.

I actually had a couple of people help me with the editing and/or proofreading of my review, and I’d like to thank Jennie-Sue, Eli, and Starchy for their offers of help.

If you haven’t noticed, I have ZERO advertising on my site. It only costs me a couple of bucks a year to keep this site going, and I didn’t want to spoil the relationship with my readers by trying to commodify their viewing. So, when I was approached to do the review, I was very specific that I would not pull any punches just because they gave me a free book. Packt also tried to sign me up with an affiliate link to the book, which you’ll notice is nowhere in this (or any) post.

As you can tell, I really didn’t use the kid gloves with this review. I’m not very happy with the general quality of Maven documentation (as I’ve noted before), and I wasn’t going to give this book high marks for being just as bad as the rest.

I did manage to sneak in (or are they clumsily manhandled?) 3 different literary fiction references, which I hope spices up the review and adds a bit of character. Let me know if you can name them.

I started out my trip in Bordeaux, where I found a pretty nice hotel to be my ‘base of operations’ whilst I tried to work out my motorcycle rental. I managed to find the website and then the physical location of Bordeaux Scooters, and this is where I rented the motorcycle for one whole week.

For the first day, I just rode around the city of Bordeaux a very little bit, trying to accustom myself to the Yamaha Fazer 650 (since I normally ride a Kawasaki Ninja 500).

On my first full day on the bike, I got out of Bordeaux and hit a bunch of secondary (C and D) roads. I hit places like Biscarosse(-en-Plage), Mimizan, and Léon, before I stopped for the night in Hasparren where I stayed at a cute Hôtes de Chambre (Bed & Breakfast). I was feeling pretty good and confident, both in my motorcycling ability and my language ability to operate in the hinterlands of France.

For my second day of riding, I figured I’d take some more scenic roads, and even cross over the Spanish border for a bit. I made it through the border just fine, and was cheerfully enjoying the nice big sweeping roads on the way to Elizondo, and then turned on the road towards Erratzu to make my way back into France near Saint-Etienne-de-Baïgorry.

It was just after a hairpin turn, not more than 1km from the French border and the summit of the hill. I noticed the old stone barn on the left side of the road, then I looked uphill and contemplated that I should be careful because of all the mountain mist that was probably making the road slippery. I brought my attention back to the road, and was alarmed to find that I had drifted close to the side of the road. I started to panic. I was so worried about the side of the road that I couldn’t look away, and motorcyclists know that’s exactly where I ended up.

Now that I was on the edge of the road, I made a snap decision to bite the bullet and take the bike off the road and try to stop before anything untoward happened. Something untoward happened. The mist I had been worrying about mere milliseconds before was coating the grass I was on and the front tire slipped sideways, dumping me and the bike onto our left sides.

I am lucky because I had just recently come out of a tight turn and I wasn’t going all that fast. I landed face down with my torso on the pavement, and did only about 1 1/2 horizontal pirouettes before I came to a rest. While the helmet I was wearing was scraping across the pavement, I remember thinking “Boy, a helmet is a really good idea!”

I was up in an instant, just in time to see that the hard case (holding most of my possessions) rolling down the hill. In my adrenaline-addled mind, I decided that I really needed to get my stuff back. So, I went careening down the side of the mountain in my full gear. I found the case 1 1/2 switchbacks down. I brought it up to the road (1 full switchback below the motorcycle) and only then did I decide to take off some of my gear and inspect for damage. Other than a little bit of scuffed up skin, I was actually fine.

As I was walking back up to inspect the bike, a younger French guy in a car stopped to give me a hand. He helped me turn the bike over, and point it away from downhill. He told me he expected insurance (assurance in French) could be found in any town, and that they’d have me set back up in no time. I thanked him for his help and advice, and sent him on his way, while I figured out what I needed to do.

After I got all my stuff assembled, and took a couple of pictures, I sat down and tried to call the rental shop. I ended up calling Ryan (in the U.K) for some research help because I didn’t know what the country-code is for France. After we got that figured out, I realized the rental shop was on their stated lunch break until 2PM. (It had just turned about 12:30PM.) I sat there for a bit trying to keep myself calm and counting my lucky stars. After I changed into some less-sweaty and warmer clothes, I decided that I should try to get to ‘civilization’, preferably on the French side of the border since the motorcycle was rented from France.

Eventually a nice (German?) couple on motorcycles stopped to give me a hand. We were formulating an elaborate me-plus-my-stuff-on-their-bikes plan, when I realized it was a bit soon for me to be riding on a motorcycle again. I got them to help me flag down a passing carpenter, who agreed to take me and my stuff in his truck to the mechanic’s in Saint-Etienne-de-Baïgorry. The local mechanic was of no help, other than trying to help me call the rental shop again, which I knew was still closed. After he basically told me to go away because he didn’t deal with motorcycles and he was on his lunch break, I walked towards town center and sat on the steps of a hotel/brasserie that was also closed for lunch. I decided to wait out the remaining hour or so until the rental shop opened up by chilling out and reading my Kindle on those steps.

Once I did get the rental shop on the phone, they told me that I needed to get the bike transported back to Bordeaux (250km) by whatever means necessary. The shop owner offered to see if he could find someone to do it, and I said I’d look around at my end. After our conversation, I had no idea if I would be stuck in the town of Saint-Etienne-de-Baïgorry overnight, but I figured I’d check into the hotel until things settled, and if I had to leave early, I could just lump one night’s charge.

As I was checking into Full-screenHotel Juantorena, I mentioned (or whined) to Mélanie (who I later found out was one of the owners) that I had just been in a motorcycle accident and needed to find a truck to bring the broken motorcycle back to Bordeaux. She said that her husband might be able to help me out. Bixente came out from the kitchen, and called around to some truck services in Biarritz, and found me a quote of €1,200. I thanked him and said I would call back to Bordeaux to see if the rental place had found me a better quote. The rental place said to call back in a couple of hours because the friend they were going to ask was out at the moment and it would be a while before they got an answer.

It turns out that Bixente is also a motorcyclist, and offered to take me (after he finished setting up his kitchen for the evening) to pick up the motorcycle on his motorcycle trailer to bring it down (the 10 km) to his hotel parking lot. I was kind of amazed at this, but just went with it after the day I was having. About a 1/2 hour later, after I had washed off some of my road rash, he called me down to the front of the hotel where he, his truck, and his motorcycle trailer were waiting for me. He drove me up to the crash spot where we loaded up the wreck, and brought it back to the hotel.

The ride up and back could have been horrible. But after figuring out my French skills needed just a bit of annunciation and a slower pace, Bixente actually took the time to get to know me. We had a really nice conversation, and I’ve come to look back upon that conversation as one of the nicest moments during my time in France.

After getting back to the hotel, I called the rental shop to tell them that the bike was now in the parking lot. In addition to the location of the bike, we had some (mis-)communication where I thought they said to wait several more hours to verify that the truck from Bordeaux would be interested in the job. So, I took a little nap, then read some more whilst having a beer in the bar. I was really surprised when Bixente told me the truck driver was at the other end of town and would be arriving soon. (Evidently, when I thought the rental shop was telling me that I was waiting for confirmation, they were actually telling me that I was waiting for the arrival of the truck.)

The truck driver, myself, and Bixente loaded up the bike into the truck. It was now about 8 or 9PM, and the driver hadn’t eaten, and neither had I, so we had dinner at the restaurant. The driver was kind of gruff, and not all that friendly, but I managed to get some small-talk in. After dinner, using Bixente as a patient go-between, we established that it was best if I went with the truck driver back to Bordeaux with the bike. (I didn’t realize there was more for me to do there.) So, I checked out of the hotel. I tried to convince Mélanie to keep my room charge, but she wouldn’t hear of it. She insisted that if I weren’t staying overnight they wouldn’t even think about keeping my money.

The driver brought be back to Bordeaux, and dropped me off at midnight at a hotel right near the rental shop. The next day, I went to the rental shop to find out that we were waiting for a verdict from the motorcycle repair shop. When I remembered that I hadn’t yet paid the driver from the evening before, the rental shop owner called him for the price. Since I was paying in cash for the truck ride, it only came out to €500, which is a great deal compared to the other quotes I had received.

Later that afternoon, the verdict came down that the bike’s frame was bent and therefore “totaled”. I went back over to the rental shop to sign the credit card slip for the €1800 security deposit that I had now forfeited. And thus ends my motorcycle adventure in France.

Looking Back

Now, people say all sorts of horrible things about the French. In general, I can tell you that much of this is wrong. In specific, I can tell you that Mélanie and Bixente are some of the warmest and most caring people I’ve ever run into in my travels. They took the time to patch up and help this stupid American with bad French and even worse motorcycle skills, and not ask for anything in exchange, other than an email greeting at some time in the future. I hugged Mélanie and Bixente fiercely, and I left their hotel with tears in my eyes because I felt really fortunate to have met these beautiful people.

I realize that I directly benefited from what I refer to as the Motorcyclist (a.k.a. Motard) Fraternity. Without knowing me, but because I spend time on two wheels like they spend time on two wheels, both the German couple and Bixente went way out of their ways to make sure I was taken care of. I guess it’s a similar thread amongst motorcyclists to help out your fellow motorcyclists.

Doing Them A Solid

In addition to adding Mélanie and Bixente to my Xmas card list, I have decided to send as many people as I can to them. So, if any of you readers are ever interested in a quaint village in the beautiful Basque region of France, might I suggest Hotel Juantorena? Also, spreading this info to motorcyclists far & wide would be much appreciated.

(I will try to scan in their pamphlet, but in the mean time, here’s their contact info:) t

Hotel Restaurant Juantorena

64430, Baigorry

Pyrénées-Atlantiques, Aquitaine, France

Lat/Long: 43.17405, -1.34875

Phone: 05 59 37 40 78

Email: hotel.juantorena@orange.fr

Their pamphlet shows that they have a website (http://www.hotelrestaurantjuantorena.fr) but it doesn’t seem to be working?

I was blown away today when I got an email from Brittany saying that not only will Widgetbox management support me in this endeavor, but they are going to add a 1 day per year allowance to our policies for all the employees to pursue similar efforts. Wow!

This just cements for me that I am totally working with the right set of people in a company that is just the right size for me. I feel appreciated, listened to, and respected, even when I bring forth crazy ideas like sending me off on our investors’ dime to save the world.

Yeah, my life: it doesn’t suck!

To get a feel for how many of these problems existed (after I just-in-time fixed the individual JSPs that crossed my path), the boss wanted me to run a precompile against our whole JSP codebase.

I found the instructions on the Tomcat site, which proved to be incomplete and/or incorrect (of course).

Here is what I ended up with:

<project name="Webapp Precompilation" default="all" basedir=".">
   <import file="${tomcat.home}/bin/catalina-tasks.xml"/>
   <target name="jspc">
       <jasper
             validateXml="false"
             uriroot="${webapp.path}"
             webXmlFragment="${webapp.path}/WEB-INF/generated_web.xml"
             outputDir="${webapp.path}/WEB-INF/src"
             compilerTargetVM="1.5"
             compilerSourceVM="1.5"
             failOnError="false" />
  </target>

  <target name="compile">
    <mkdir dir="${webapp.path}/WEB-INF/classes"/>
    <mkdir dir="${webapp.path}/WEB-INF/lib"/>
    <javac destdir="${webapp.path}/WEB-INF/classes"
           optimize="off"
           debug="on" failonerror="false"
           srcdir="${webapp.path}/WEB-INF/src"
           source="1.5"
           target="1.5"
           excludes="**/*.smap">
      <classpath>
        <pathelement location="${webapp.path}/WEB-INF/classes"/>
        <fileset dir="${webapp.path}/WEB-INF/lib">
          <include name="*.jar"/>
        </fileset>
        <pathelement location="${tomcat.home}/lib"/>
        <fileset dir="${tomcat.home}/lib">
          <include name="*.jar"/>
        </fileset>
        <fileset dir="${tomcat.home}/bin">
          <include name="*.jar"/>
        </fileset>
      </classpath>
      <include name="**" />
      <exclude name="tags/**" />
    </javac>
  </target>

  <target name="all" depends="jspc,compile"></target>

  <target name="cleanup">
        <delete>
        <fileset dir="${webapp.path}/WEB-INF/src"/>
        <fileset dir="${webapp.path}/WEB-INF/classes/org/apache/jsp"/>
        </delete>
  </target>
</project>

The real stroke of luck is this piece:

             compilerTargetVM="1.5"
             compilerSourceVM="1.5"

Their document said stuff about adding some parameters (source="1.5" target="1.5") to the “javac” target, but they neglected the “jasper” target. The error messages complained about the above two parameters being set to 1.4, so as an experiment I plugged them into the ANT target with 1.5’s and the compilation ran correctly!

Another word of note, the “showSuccess” directive did not work as their documentation states, but the “failOnError” directive does.

I hope this helps others!

I do not like Facebook. I do not like it one bit. I want nothing to do with Facebook at all, and I’ve been very adamant about not signing up for an account despite the urging of everyone and their brother.

So, when I recently gained an understanding of how Facebook Connect works, I got a bit upset. Let me show you why with an example.

Let’s say I want to create an account at MapMyRun.com which implements Facebook Connect, I will use my primary email address of “nelz@example.xxx”. After my account gets created MapMyRun then encrypts my email address with a one-way hash, which for the sake of argument looks like “BIGBADHASH”, and sends this hash to Facebook. “So what?” you think. Sure, they can’t figure out anything about me from a single one-way-hash of my email address, right?

Well, then let’s say I register for an account at io9, again with my primary email address “nelz@example.xxx”. Since io9 also implements Facebook Connect, they also hash my email address and send it to Facebook. Guess what? The resulting string, “BIGBADHASH”, is the exact same as what MapMyRun just sent them.

Now, Facebook knows that someone with an email address that hashes to “BIGBADHASH” has an account on both MapMyRun and io9. Again you think “So what?” That one-way-hash protects my identity from being associated with any of these specific behaviors, right? Au contraire, mon frère.

Now one of my well-meaning friends, who doesn’t know how much I loathe Facebook, tells Facebook that they want to connect with someone at the address “nelz@example.com”.

This was the last piece of the puzzle that Facebook needed. Facebook need only apply the one-way-hash to the plaintext email that my friend just provided them with, and they get “BIGBADHASH”. Then, they look up in their database where they’ve seen that hash before, and now they know that a user with an email address of “nelz@example.com” has an account on both MapMyRun and io9.

Now I, who has never ever logged into Facebook, am getting tracked by Facebook whether I like it or not.

External Remediation

Okay. So what can we do about this?

I looked on Facebook.com, and I found a Privacy Policy. But everything on there requires that you have an account on Facebook. I guess I could create an account, then delete it, but I don’t want an account on Facebook! What Facebook really needs is some web form for non-members that says “Forget anything you have, or will, ever collect about email XYZ”. But, that’s not likely to happen.

What about the end-points, the sites that are implementing Facebook Connect? Personally, during their sign-up processes, I’d like to see a check box that says “Don’t sell me out to Facebook.” Again, that’s not likely to happen.

Personal Remediation

Now, don’t get me wrong, I’m not a n00b. I realize there are all sorts of sites tracking my footprints across the digital landscape every day. (Quantcast, DoubleClick, etc…) For most of them, if I were paranoid and technical enough I could purge their cookies or set up a proxy that doesn’t let my browser connect to those URLs.

But this Facebook thing is different, because it’s highly likely that the communication back to Facebook is not coming from my browser, but from the servers of sites like io9 and MapMyRun. And I have no way to stop it.

How about using a different email address for each site. Sure, that could work. If I had my own mail server, I could create “io9@nelzserver.xxx” for io9 and “mapmyrun@nelzserver.xxx” for MapMyRun, but how many people will have access or technical ability for something like that?

Gmail has a feature that could help out here. If I have an email address like “example@gmail.com”, I will still get the mail if it is sent to “example+io9@gmail.com” or “example+mapmyrun@gmail.com”. I found two challenges with this pattern: 1. it can break the “Forgot My Password” functionality if you forget what email you signed up with, and 2. emails with “+” in them don’t always pass the (incorrect) regex’s sites use to validate emails.

Conclusion

As I have said before, I am living life pretty openly on the internet. And like I said above, I know there are countless other companies doing much more specific tracking and profiling of me.

But Facebook’s hegemonic desires to run the internet frustrate me, and I don’t want to be a part of it. And it pisses me off that there’s nothing I can do to extract myself.

Update: Found this interesting blog post – “Dark Stalking on Facebook“

So, here is the short version:

1. Have Rocking Goals
2. Be Ambitious
3. Invest In Yourself
4. Healthy Lifestyle
5. Be Responsible
6. Patience Is The key
7. Never Give Up
8. Learn From Failures
9. Remain Positive
10. Celebrate Success

Normally at this time of year, I would be in full-on packing mode for Burning Man. Alas, my best friend from college decided to get married on the day the Man burns (in the U.K.). Then, to top it all off, my brother decided to get married on the 18th of September in Boston. This left me with little to no obligations from the 7th to the 17th of September, so I decided that I was going to rent a motorcycle and tour around the south of France.

What does a techie do when they plan a trip? They buy tech gadgets of course!

My first purchase was a netbook. I got an Asus EeePC 901 (Linux). I opted for the white model, because there was a $300 (100%) ‘black tax’. I opted to get some scull vinyl stickers ($13) instead. I dumped the default Xandros OS and installed Ubuntu.

My original thought was that I didn’t want to be tempted to work on work or side projects while I was traipsing around Europe, so I got a solid netbook that could provide me with email/Twitter/basic web surfing, but would lend itself to opening up an IDE. After a while, I realized that I should reserve my vacation for things I *want* to do, even if it includes working on a software
project. So, I’ve decided to forget the netbook and take my home laptop, a 15″ MacBook. (If you are reading this and want the netbook I described above, I have one for a decent price if you’d like it.)

The second bit of tech that I purchased was a Kindle (2nd gen, non-DX). I do enjoy ‘personal’ reading, but rarely take the personal time for it (except on vacations) because I’m usually caught up in some technical book. My usage of it has waxed and waned since my purchase, but it definitely addresses my criteria of reducing the amount of ’stuff’ that I am carrying whilst on-motorcycle in France. I do plan to put some entertaining books on my Kindle before I leave. (“Necronomicon” anyone?)

So, I’m down to my Kindle and my MacBook. What about my G1 mobile phone? Well, the surprising thing is that I’ll probably just stick to my current provider (T-Mobile). I was aghast when I heard their prices (something like: $0.99/min of phone usage, $0.35 per sent text message, free received text message, $0.35 ‘connection charge’ [for every time the phone checks for messages?], $15.00 per Megabyte of data), but in my subsequent research that’s about par for the course for prepaid SIM cards. I don’t like it, and I’m dubious that this is as good as it gets, but I don’t have the time or the inclination to fight
it too hard. I just have to accept that my Twitter addiction may cost me some. One of the positives though, is that when I told T-Mobile that I was considering using GSM cards purchased abroad they offered to help me unlock my phone. That should be a boon for me when I decide to replace it in the future and want to sell it.

I’m not planning on taking a camera, other than my G1 and my laptop. I am kind of hoping to take some videos using my MacBook’s built-in camera, but we’ll see if that even happens, because for most of my life I’ve been a forgetful and shitty photodocumentarian, and I don’t see that magically changing for this trip.

During my ‘where the wind blows’ tour of France, I’ll probably use CouchSurfing.org to meet people, or possibly even find shelter if I can plan that far in advance, but I’m purposly keeping my schedule unplanned so I don’t know if I’ll want to subject CouchSurfing hosts to my slapdash planning. The housing may just end up being, in order of preference: couches, hostels, B&B’s, or hotels. Like I said, I going *very* unplanned. I think I should be okay, because the annual French
holiday season is mostly done by the beginning of September. If not, it’ll be an exercise in creativity, right?

I’ve got 3 projects to work on while travelling. Firstly, I have visions of a Simple-Spring-Memcached v2, and I’ve already made a bit of progress starting that. Next, there is my as-yet-unannounced Ruby-on-Rails, Twitter based web service. And thirdly, I’ve decided that I want to do a presentation at Silicon Valley Code Camp in October about Simple-Spring-Memcached, and I can work on that presentation for a bit if I’m bored.

So, that’s my story. If I do get around to photodocumenting (or videodocumenting) any of my trip, I’ll be sure to post a link here.

Take the Maven Tomcat Plugin for example. It sounds so nice to just type “mvn tomcat:run” in your webapp module, and have it automagically run, dynamically loading any JSP changes. But, if you have a non-trivial webapp, you probably need to send in some system properties.

Let’s pretend that I require the following command-line parameters passed to Tomcat on the command line:

-Dexample.value.1=alpha -Dexample.value.2=beta

How would I send that in to the Tomcat plugin? Well, the documentation says there is a “systemProperties” element where you can sent them in. But what is the format?

Is the format perhaps like the Surefire Plugin?

<systemProperties>
  <property>
    <name>example.value.1</name>
    <value>alpha</value>
  </property>
  <property>
    <name>example.value.2</name>
    <value>beta</value>
  </property>
</systemProperties>

Or perhaps the format is like that of the Jetty Plugin?

<systemProperties>
  <systemProperty>
    <name>example.value.1</name>
    <value>alpha</value>
  </systemProperty>
  <systemProperty>
    <name>example.value.2</name>
    <value>beta</value>
  </systemProperty>
</systemProperties>

Nope. The format is like neither of those. It’s like this:

<systemProperties>
  <example.value.1>alpha</example.value.1>
  <example.value.2>beta</example.value.2>
</systemProperties>

I’ll admit that this format is a bit less verbose. But why, in the name of all that is holy, does it have to have it’s own 1-off syntax?!? And can you find this documented anywhere else? I was sure challenged finding it.

This is the kind of non-documentation and irregularity that gives Maven a bad name and keeps my blood pressure high.

UPDATE (1 Nov 09): As she says in the comments, Kathy actually took the time to submit a ticket to the Maven Tomcat Plugin maintainers, rather than going with my tactic of passively bitching. And today I get notified by herion that the suggestion was taken and there is now public documentation added about these properties.

http://www.palfrader.org/code2html/code2html.html

We opt to have all of our modules stay in lock-step version-wise, so we keep a pretty large structure in our SVN trunk. We include/exclude modules for compilation by using Maven profiles, so we don’t have to build the whole structure if we are only changing one small component. Our top-level pom.xml file looks similar to this:

<project>
  <groupId>...
  <artifactId>...
  <version>...
  <packaging>pom</packaging>
  <modules>
    <module>baseModule</module>
  </modules>
  <profiles>
    <profile>
      <id>all</id>
      <modules>
        <module>otherModule</module>
        ...
        <module>web-test</module>
      </modules>
    </profile>
    <profile>
      <id>web-test</id>
      <modules>
        <module>web-test</module>
      </modules>
    </profile>
  </profiles>
</project>

As you can see, running “mvn clean install” at this top level would only end up building the baseModule. To get all the modules, we run “mvn clean install -Pall” which builds baseModule along with otherModule and web-test and anything else as represented by the ellipse. The web-test module is the one we will be interested in.

For our heavy-weight tests (non-unit tests, like functional or web testing), we like to have the module compile, but not run unless we specifically trigger the tests. To achieve this, we create a pom.xml (for the web-test module) that looks something like this:

<project>
  <parent>...
  <artifactId>web-test</artifactId>
  <packaging>pom</packaging>
  <build>
    <testSourceDirectory>src/it/java</testSourceDirectory>
    <testResources>
      <testResource>
        <directory>src/it/resources</directory>
      </testResource>
    </testResources>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>2.0.2</version>
        <configuration>
          <source>1.5</source>
          <target>1.5</target>
        </configuration>
        <executions>
          <execution>
            <goals>
              <goal>testCompile</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.4.2</version>
        <configuration>
          <testSourceDirectory>src/it/java</testSourceDirectory>
          <excludedGroups>web-test</excludedGroups>
        </configuration>
        <executions>
          <execution>
            <phase>integration-test</phase>
            <goals>
              <goal>test</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>

This pom has several features:

• It sets up src/it/java as the location holding the source code for the tests
• It sets the surefire plugin (which runs your tests) to only run at the integration-test part of the Maven lifecycle
• It says to ignore any tests in the TestNG “web-test” group
• Note the packaging says this module is of the type “pom”. I found that if this is set to “jar”, the tests run twice for some unknown reason

Now, if you had tests in src/it/java (that were all annotated as “web-test”) and you ran “mvn clean install”, you’d see that zero tests ran. This is what we want! Now, we have to get the tests running if we pass a specific profile in. To achieve this, I added the following profile definition to the web-test pom.xml.

<profiles>
    <profile>
      <id>run-web-test</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.4.2</version>
            <configuration>
              <suiteXmlFiles>
                <suiteXmlFile>src/it/resources/testng.xml</suiteXmlFile>
              </suiteXmlFiles>
              <!--<groups>web-test</groups>-->
              <!--<forkMode>always</forkMode>-->
            </configuration>
            <executions>
              <execution>
                <phase>integration-test</phase>
                <goals>
                  <goal>test</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

This profile is invoked when you run “mvn clean install -Prun-web-test”. There are several things I’d like to point out here:

• At runtime, this overrides the previously-declared surefire plugin configuration, but only when invoking the profile.
• Originally, I was mostly getting stuff to work without the <suiteXmlFiles /> section, but with the <groups /> and <forkMode /> sections… But it was running every single test class as it’s own TestSuite.
• To fix the multiple TestSuite (and @Before*, @After* problems that I’ll discuss later), I ended creating my own testng.xml file. Having this file and using the <suiteXmlFiles /> element made things a whole lot easier for configuring my TestNG executions than trying to configure the tests through the clumsy interference of the surefire plugin.
• As much as I like Maven, I have to say that the lack of documentation and general obfuscation that happens when using their plugins can really drive a person BATTY!

Now, I need to start integrating the stuff I need for using SeleniumRC. I found some decent help on how to start up and shut down the selenium-server, however I disagree with using a post-integration-test phase to shut down the server, because if the tests fail in the integration-test, Maven won’t progress to the next phase and you’ll be left with a spuriously running selenium-server. The client API’s do have access to the command that the was being run to shut the server down, so it is just a matter of having some TestNG @AfterSuite or @AfterGroup method issue the Selenium.shutDownSeleniumServer() command.

This brings me to some of the TestNG wonkiness I saw. I decided to use a Singleton Data Provider (named  SeleniumFactory) to deliver the Selenium objects to the individual tests. (Selenium objects are time-expensive to create, so I wanted to only create 1 for the duration of the entire test suite.) I wanted to initialize the SeleniumFactory object in a @BeforeGroup method, deliver the Selenium object as a Data Provider, and then tear the SeleniumFactory down in a @AfterGroup method. (At first, I was fighting Maven’s handling of each test as its own test suite which was giving me sequence issues, which is why I ended up defining my own testng.xml file, as I stated above.) Let me start with some code to show you what I mean:

public class SequenceEndsTest {
    @BeforeGroups(groups = {"web-test"})
    public void startupSelenium() {
        System.out.println("-- > Called startup.");
    }
    @AfterGroups(groups = {"web-test"}, alwaysRun = true)
    public void cleanupSelenium() {
        System.out.println("-- > Called cleanup.");
    }
}
public class SeleniumFactory {
    @DataProvider(name = "selenium")
    public static Object[][] getSelenium() {
        System.out.println("-- > Called data provider.");
        return new Object[][] { new Object[] {null}};
    }
}
public class SequenceTest {
    @Test(groups={"web-test"},
            dataProvider = "selenium", dataProviderClass = SeleniumFactory.class)
    public void testSomething(final Selenium selenium) {
        System.out.println("-- > Called test.");
    }
}

This is what I expected to see after running this code:

-- > Called startup.
-- > Called data provider.
-- > Called test.
-- > Called cleanup.

But this is what I *actually* saw:

-- > Called data provider.
-- > Called startup.
-- > Called test.
-- > Called cleanup.

I would have assumed that an @BeforeGroup method got called before a data provider method, but I guess my assumption is wrong, eh? After I figured out this order-of-method-calls business, I was able to adapt my SeleniumFactory accordingly.

… And that is my story. To summarize: each of these tools could be better documented, but at the end of the day I was able to get a Maven module up and running SeleniumRC tests via TestNG. Now, on to the test-writing!

#1 (“Its not a relational database.”) is very, very important. You’ve really got to stretch your brain a bit to get out of the RDBMS headspace to see how it can be beneficial. Everything is stored as a string, so if you want to any kind of sorting with regards to numbers or dates, you have to format the values to be sorted lexicographically. (This reminds me of when I was working with Lucene.)

In addition to not having any kind of auto-increment (as mentioned in that blogs #5 point), there is no concept of an “increment” operation on a field. At first I was tempted to try for a Read-Increment-Update pattern, but if you think of how that would interact with Amazon’s concept of Eventual Consistency (which, for some inexplicable reason, I find absolutely hilarious), you will realize this is a sub-optimal pattern for data integrity. (The pattern I ended up using lends itself only to the specific interaction patterns I am designing for, so I won’t bore you with the details.)

Though there is no auto-increment, many blog posts have been published recommending UUID’s, which seems to be working for me as well.

As for that blogs #8 point, there is now a offered called Javascript Scratchpad for Amazon SimpleDB, which is just a small set of HTML/JS pages that you save locally and run in a browser. I think it’s actually a pretty cool lightweight and simple GUI tool to offer.

Looking at the price list, you might think that SimpleDB could get expensive fast. But, if you read carefully you’ll see the following: “Data transferred between Amazon SimpleDB and other Amazon Web Services within the same region is free of charge (i.e., $0.00 per GB).” That’s pretty cool. As long as whatever is hitting your SimpleDB instance resides on the Amazon cloud (in the same region), you don’t pay for data transfer.

I also gotta comment on the Java client provided by Amazon. Yeah, it works, but working with it is fairly “meh”. You get the source an everything for it, but it’s not Open Source and they definitely don’t give the impression that they’re looking for any contributions. I would’ve submitted a couple of lines of documentation for some of the methods at the very least.

I’ve heard some good things about the typica library, specifically that the interaction patterns with the library are nicer than the Amazon-provided library. There only seems to be one (maybe two?) developer working on it, but at least it’s hosted on Google Code so, unlike Amazon, maybe the developer would welcome contributions.

I haven’t used typica myself yet, but since I’m not too far down the other path, maybe I’ll check it out.

Background

I started this blog way back in the beginning of 2007. At the time, I wanted more than just a blog host, I wanted a host where I could deploy other Java webapps if I felt the need. (For other side projects, y’know.) Following the lead of Matt Raible, I chose KGBInternet to host a Roller (which wasn’t then, but is now an Apache project) blog instance. Keith, the proprietor of KGBInternet, is incredibly responsive and I’d have to say that his service was a great $20/month host where you get full command-line access and control over your JVM/Tomcat instances.

A couple of months ago, I decided to critically look how I use my different online providers.

I had been maintaining a cheap, $5/month GeekISP account for personal data SVN hosting/backup. Since most of my projects are Open Source (and usually hosted on Google Code), I realized I wasn’t really using my account, so I dropped it.

And when I critically looked at my usage of KGBInternet, I realized that I was only using it for maintaining my blog. That’s $240 (Candian) bucks per year for blog hosting, which could be done for much less by another provider. So, I decided to drop that account.

Getting Data Out Of Roller

The biggest problem I had was trying to get my blog content out of Roller. There is no “Export” functionality, which frustrated me to no end. I found a posts with a tutorial on how to export directly from the database, but that wouldn’t work from me because 1) I didn’t want to go through a PHP export process, and 2) my db entries are all in JSPWiki markup (via the Roller JSPWiki plugin). I found another post showing how to get my data out using Roller templates, but that wasn’t going to specifically work for me, since I wasn’t going to be hosting my own WordPress install. However, the concept of using the built-in Roller template capabilities had a bunch of potential.

At this point, I wasn’t yet sure if I was going to end up using WordPress.com or Blogger. My investigations proved that Blogger only likes to import/export in their own format, for which I could find no documentation. WordPress however has several import capabilities, so I figured I’d target WordPress, and maybe use some of the community WordPress -> Blogger converters if I needed to move my stuff over to there.

WordPress has its own WordPress eXtended RSS (WXR) syntax, but it’s not easy to get a definitive format information. WordPress will import from a MoveableType export file, which is actually very well-documented. This is what basically decided me on moving to WordPress, at least for the time being…

By referring to both the MoveableType documentation and the Roller templating guide, I was able to create the following template:

 1  #set($pager = $model.getWeblogEntriesPager())
 2  #set($map = $pager.getEntries())
 3  #foreach( $day in $map.keySet())
 4  #set($entries = $map.get($day))
 5  #foreach( $entry in $entries )
 6  TITLE: $entry.title
 7  AUTHOR: nelz9999
 8  DATE: $utils.formatDate($entry.pubTime, "MM/dd/yyyy HH:mm:ss")
 9  CATEGORY: $entry.category.name
 10  -----
 11  BODY:
 12  $entry.transformedText
 13  #foreach( $comment in $entry.comments )
 14  -----
 15  COMMENT:
 16  #if ("$comment.name" != "")
 17  AUTHOR: $comment.name
 18  #end
 19  DATE: $utils.formatDate($comment.postTime, "MM/dd/yyyy HH:mm:ss")
 20  #if ("$comment.email" != "")
 21  EMAIL: $comment.email
 22  #end
 23  #if ("$comment.url" != "")
 24  URL: $comment.url
 25  #end
 26  $comment.content
 27  -----
 28  #end        
 29  --------
 30  #end
 31  #end

One of the keys in the above template is Line #12. Instead of using “$entry.text”, I use “$entry.transformedText”, which applies all the JSPWiki formatting. (And, if you’re copy/pasting this template, be sure to update the “AUTHOR:” tag on Line #7 to something appropriate for you…) Keep in mind that this gets you one page of (published, not draft) content at a time, as defined by the “Number of entries to display on weblog” parameter in the Preferences -> Settings tab. You get to later pages of data by appending “?page=X” (0 being the default) to the URL: “http://nelz.net/roller/nelz/page/moveabletype.tmpl?page=1″.

It is then a simple matter of doing a “wget” for each page: “wget http://nelz.net/roller/nelz/page/moveabletype.tmpl?page=1 -O page1.txt”. If you have lots of posts, I’d recommend upping your entries/page setting, so you have less individual files to manage, but also beware of your file sizes getting too big… I left my entries/page setting at 10, and I ended up managing 14 files. Had I set it to 50 entries/page, it would have been only 3 files.

But, now you’ve got most of your content (not images and stuff tho) in a portable format!

Getting Data Into WordPress

After creating my WordPress.com account, it was pretty simple to get the data in, via the Tools -> Import menu. Now, I had 138 posts in Draft status. I tried using the bulk edit -> publish tool, but for some reason that wasn’t working for me. I published a couple by hand, but then I remembered back to something Neil Ford said at a conference I attended: “our computers get together and laugh at us at night because we keep doing their (repetitive task) jobs for them…” Well, I’ll be damned if I let my computer laugh at me!!

So, I popped open SeleniumIDE, and created a quick little automation to approve all the drafts in my queue, a single iteration of which looks like this:

<tr>
 <td>open</td>
 <td>/wp-admin/edit.php?post_status=draft</td>
 <td></td>
</tr>
<tr>
 <td>click</td>
 <td>link=Quick Edit</td>
 <td></td>
</tr>
<tr>
 <td>select</td>
 <td>_status</td>
 <td>label=Published</td>
</tr>
<tr>
 <td>click</td>
 <td>link=Update Post</td>
 <td></td>
</tr>
<tr>
 <td>waitForText</td>
 <td>//img[@alt='More stats']</td>
 <td></td>
</tr>

This worked swimmingly, and in 30 minutes or so, I published nearly 140 posts “by hand”.

Getting to know Wordrpress

Things that I like about WordPress:

• It is a much better interface than Roller
• “Pages”. I also use my blog as a place to keep an online version of my resume, and Pages allow me to exactly do that without having to use a ‘regular’ blog post that I update over time.
• WordPress automagically figures out how to map the old Roller URLs to the new ones. I was getting quite a few links to some of my recent posts, and I really happy that the links floating around the web-o-sphere will still work. (E.g. “http://nelz.net/roller/nelz/entry/velocity_conference_recap” ends up on the page “http://nelz.net/2009/06/25/velocity-conference-recap/“.)
• Setting up my own domain was absolutely painless.

Things that I haven’t yet decided on:

• You can’t use Google Analytics on a WordPress.com blog, but they do provide some of their own stats (and there are several other options as well). I haven’t yet decided if it’s better to have the stats easily available in my blog admin, or if I’d have preferred to keep all my analytics stuff together in Google.
• I haven’t yet purchase the $30/yr no ads upgrade. I haven’t seen any ads on my site as it is, so I’m not sure if I will actually need it?
• No specific control over robots.txt. Whereas I want 99% of my blog public, I want to prohibit Google from picking up my resume, ‘cuz I kinda hate cold-calls from recruiters (but maybe I’m just being silly).

To Do

• Some of the formatting (especially on the preformatted code sections) got lost in the migration… I’ll try to go back to the most used ones to reformat.
• I gotta update that resume of mine.
• Once I’ve been up on WordPress for a week or two, I’ll actually cancel my account with KGBInternet.

General Themes

• I had never heard of it before, but almost every single presenter referenced Ganglia as a de-facto monitoring system.
• It got presented a bunch of different ways, but basically all the big sites that presented stuff today all use on and off (or dial-able) configurations for features. This is not just for release-time of new features, but this can also help them manage their capacity if something is going wrong.
• Many of these talks are available online: http://velocityconference.blip.tv/

“Image Weight Loss Clinic” at Ignite Velocity

• Stop using GIFs. Use PNGs.
• Use data strippers/filters on JPGs. There is a lot of ‘extra’ data included in JPG that aren’t necessary.
• There are bunches of PNG optimizers out there. We should use at least one, if not all of them. (The suggestion was to build a serial pipeline for them.)
• Using the Velocity page as an example, the presenter was able to reduce the page weight by 30% following these suggestions.

The User and Business Impact of Server Delays, Additional Bytes, and HTTP Chunking in Web Search

• A lot of people loved the empirical data showing that slower sites cost you users, even for differences as small as 200ms. Brady Forrest wrote up a great digestion of this talk: “Bing and Google Agree: Slow Pages Lose Users“
• The technique that I pulled outta the whole deal is to use HTTP 1.1 Chunked data. This enables a site to deliver the easy-to-compute stuff first (static header?), and the harder-to-compute stuff later.

Fixing Twitter: Improving the Performance and Scalability of the World’s Most Popular Micro-blogging Site

• Uses NTT America managed hosting
• Put Google Analytics on 503 (Fail Whale) and 500 (Robot) pages. Use Google Analytics for failure metrics.
• Configuration Management: Do it ASAP, early & often, ‘cuz you’re gonna need it eventually
• Even their Ops stuff is checked into SVN, and they require code reviews on all their stuff, enforced by SVN pre-commit hooks and using Review Board
• Send emails (or ANYTHING ELSE POSSIBLE) asynchronously
• They recommend using “mkill“, which monitors for long-running queries and kills them, before the queries kill your site.
• Instrument EVERYTHING for timing/performance.

2 Years Later, Loving and Hating the Cloud

• Presented by an engineer from Picnik. They run a hybrid (part-cloud, part managed) site.
• Queues scale nicely in AWS. (I.e. if you are falling behind processing your queue, it is nigh trivial to just bring up another box to deal with the queue.
• In the cloud, you can plan for your average usage, and scale up/down as needed easily. (You don’t need to keep the 6th box at 1% utilization up, do you?)
• Buy hardware in batches, it gives you flexibility. No scrambling if you need a new box when there are extras around. Also waiting for good deals on price fluctuations on hardware.
• If you don’t have a good deletion plan on S3, it can end up costing you $$
• Being in the cloud enables you to ignore the S3 space problem, operationally at least, until it is too expensive (leaving you opportunity to work on other low-hanging fruit)
• Whereas you can get some nice SLA’s when dealing within your own network, latency should be treated as a complete unknown in the cloud.
• Be prepared for some difficult and juicy debugging when using the cloud.

Page Speed

• Twitter is a fantastic feedback mechanism, more so than Google Groups / wikis / forums (me: lower barrier for commentary?)
• Browser Tool like Firebug
• Someone (on Twitter?) made a very apt comment that it’s kinda sad to see Google (Page Speed) and Yahoo! (YSlow) shepherding similar projects, without trying to combine them.

10+ Deploys Per Day: Dev and Ops Cooperation at Flickr

• Websites pretty much always ship trunk. Having versions and point releases are vestigial remnants from old shrink-wrapped product lifecycles.
• “Dark launches”, where you use the on/off/variable conditionals to exercise the new backend before it becomes mission/feature-critical.
• Have all deployments notify IRC/IM/Twitter (to internal teams only) so EVERYONE knows what’s going on. Also, keep it around w/timestamps, and make it searchable
• Give ALL developers (at least read-only) access to the prod machines. It helps them help you (Ops) better.
• If there is an outage, EVERYONE stops working on new work. Even they aren’t directly responsible, JR engineers should be working to understand why something is broken. This is a good time for them to learn these diagnostic skills.
• AUTOMATE your INFRASTRUCTURE!!

Scaling for the Expected and Unexpected

• ‘Planned Degradation’ – switch off functionality, this can lighten the load on the back end
• If you hit high (un)expected load it is usually on a single/few page(s), route to a static copy of that page, regenerate every X minutes.
• The simple act of using a proxy server between your appServer and the outside world, even if it is not caching (like Squid/Varnish), is that the appServer is just delivering to a network neighbor, reducing its thread pool contention. This simple fact can have a great positive effect on your server performance.
• Watch out for cache stampedes.
• 3rd Party Resources – Load last, place at bottom of page, in an iframe. If sales doesn’t like it, tell them to go to hell. (Me: whoa.)

Infrastructure in the Cloud Era

• (Me: There were some great slides here, I hope they post them publicly.)
• With provisioning becoming so quick (minutes), we need a quicker way to get these provisioned machines up and running quickly to realize those benefits.
• The real benefit of the cloud is not $$, it is TIME (which you can turn into $$).
• Definition – meatcloud: the humans that run your cloud presence. Noticeably difficult and slow to provision a new resource in your meatcloud.
• A bit of operational philosophy – once you get your provisioning/setup all automated and quick, if a service is misbehaving have a bias towards killing it and recreating an instance, rather than trying to ‘recover’ the problem box.
• When you’ve got Command & Control systems in place, they also need an on/off switch, because sometimes you *do* need to do some manual stuff.

Ajax Performance

• Modify your nodes before you attach them to the DOM. Modifying them after can trigger cascading re-parsing by the browser.
• While most languages have Optimizers, JavaScript doesn’t. You should remove your own common subexpressions / loop invariants / etc.
• Prefer “[array, of, strings].join()” over “array + of + strings” because the “+” operator builds lots of spurious interstitial objects

Building OpenDNS Stats

• This talk was about a High-Write environment, which isn’t as applicable to Gallery, but is applicable to our Metrics app
• Don’t use auto-increment in a high-write environment, as it does a table_lock

Load Balancing Roundup

• This presenter is a committer for Perlbal and was very up-front that this talk would be heavy on the praise for it.
• Graphs that look at load every 30 seconds or more DON’T give you enough info about load on your server. Presenter suggests you watch “top -d 0.5″ for a while to get an idea of your server’s load.
• Presenter and audience agreed that HAProxy doesn’t work with “keep-alive”

I submitted the talk "Adopting SF Prankster Culture – One geek’s 10-year journey to find an outlet for his social creativity." I have posted the slides, but unfortunately those slides don’t convey a lot of information without my running commentary. I would have posted a video, but there was some problem with the video recording at the event, so I don’t think I’ll have access .

It was a really fun time. I did get a bit nervous ahead of time, but I just had to remind myself that I had just jumped out of a plane two days earlier. With that perspective, I was able to take the stage pretty confidently.

I did have a bit of a false start though, because the slides that were on the monitors right when I started were for another presenter. I did my best to bullshit my way through a slide or two until the organizers figured out the glitch. I think this actually softened up the audience with a bit of humor, which got them ready for my talk which I gave one deck later.

Doing the talk had some unexpected benefits too… For the whole next day that I was at the Velocity conference sessions, people would come up to me in the hallways and congratulate me for my presentation. I felt kinda like a geek rock star!

So if you have a chance, I would totally recommend doing an Ignite talk. I’m glad I got to ‘cut my teeth’ doing a talk on a social concept as practice in case I end up making a presentation on any of my other more technical projects.

Firstly, when talking about (capital ‘B’) Booleans, it is possible to achieve a trinary state object: TRUE/FALSE/null. However, it is not recommended. In fact, I’d go so far as to recommend breaking the fingers of anyone who tried to perpetrate this horrible pattern in your code.

Secondly, I’d like to discuss booleans in your model objects. I agree that it frequently seems like a good idea to include one in your model object. However, I have seen so many occurrences where, over time, it becomes necessary to add a third (or fourth, or fifth) state. Even the RDBMSes are hedging their bets by storing boolean flags as TINYINTs. I would suggest that you seriously consider using an Enum to represent your two states as they exist at the beginning of their lifecycle… This way you won’t get stuck with a bunch of isXXX() accessors that all have to be refactored as soon as you add a third state.

The inspiration came to me while working with memcached and the spymemcached client for Widgetbox.

I have gotten the code to the point where I feel it is good enough for prime time, so tonight I cut a 1.0.0-RC1 branch.

I’m not going to go into great detail here, as it would be a repeat of what I put up as the projects documentation. But please feel free to visit the project page and let me know what you think!