First, sorry about this getting posted prematurely through the DLTJ blog. I was trying the post-from-Flickr function, and it was telling me that the posting wasn’t working. So, it got posted here twice. And it got posted before I was ready; I was hoping it would land in the draft queue so I could edit it with further commentary. Oh, well; live and learn.
FriendFeed went live yesterday with changes to the user interface and back-end systems. The changes were moderately positive, taken as a whole, but there are aspects of the new user interface that I don’t like — the color scheme, the removal of the service icons, and the (over)-use of whitespace. Fortunately, with Firefox plus a few extensions as my primary browser, I’m able to tweak the interface to be closer to my liking. If your tastes resemble mine, I both feel sorry for you and want to help you improve your view of FriendFeed.
In this How-To guide, I show a combination of software and configuration to clean up URLs by removing the port numbers of the Java servlet engine (Tomcat) and the context path of the application. The goal is to create “cool URLs” that are are short (removing the unnecessary context path) and follow conventions (using the default port “80” rather than “8080”). OhioLINK also uses a custom access control module — built for Apache HTTPD — which makes the fronting of Apache HTTPD for Tomcat even more desirable.