Summersault Weblog

A friend recently noted that 4 of the 5 web-based applications he uses on a regular basis to manage his life are officially still in “beta” status. While I think this has become a fairly standard practice for many web application providers, I hope it’s one that we still treat with some healthy skepticism and concern.

At Summersault, when we develop software applications, beta is certainly one of the stages that the software goes through, but it’s not a stage we would ever turn the public loose on. Generally speaking, here are the stages of our software life-cycle:
Read the rest of this entry »

I recently found a neat little application that has been useful both at work and in my at-home computing. It is called Prism, and what it does is allow you to run your favorite web applications (Remember the Milk, Facebook, Google Calendar, etc.) as if they were desktop applications. Because it was built on the Firefox engine, it will run any web applications you can run in your Firefox browser.
Read the rest of this entry »

As we’ve built Summersault’s web hosting infrastructure over the years, I’ve had a great time learning all about the security and privacy issues that come with managing a complex network of computer servers connected to the Internet. Of course, it didn’t begin there - part of being a good geek has always meant showing curiosity in how things work and what’s going on behind the scenes, and I can’t remember a time I haven’t enjoyed testing the boundaries of how secure various systems are. Perhaps that’s why I very much enjoyed Bruce Schneier’s book Secrets & Lies, a formalized (but accessible) look at of a lot of the security concepts and practices I’ve encountered over the years.
Read the rest of this entry »

The IMail Server from Ipswitch software is a business-oriented e-mail management system that runs on the Windows operating system. A few years ago, we were hired by a local Internet Service Provider, Parallax Systems, to help migrate their IMail Server system to a new mail server using qmail and vpopmail on a Unix-based operating system, one of the most popular mail management system setups on the Internet.

As a part of that process, we created a Perl script to assist with the migration of all the virtual domain data, individual user mailboxes and preferences, forwards, aliases, address book files, etc. It uses the Windows registry key maintained by the IMail software and creates equivalent configuration settings under the qmail/vpopmail setup.
Read the rest of this entry »

Today’s local paper has a story about a software glitch at the Meijer big-box grocery stores that caused them to ring up all store purchases at half price. From the article:
Read the rest of this entry »

As a software engineer, one of the genres of programs that you’re always on the lookout for is the “killer app,” the tool or utility that immediately becomes the “best in class” for a given problem space and technology. One problem space where I’ve been hoping for just such a tool to come along is answering that age old question, “how can we quickly schedule a meeting between a bunch of people with separately maintained and very busy calendars?” In the past, it meant lots of back and forth conversations, disjointed calendar checking, and that sense that you were spending time on “administrivia” when you could be out enjoying the world.

Enter the free web tool Doodle.ch.
Read the rest of this entry »

Mark hasn’t had time to create a weblog entry about this yet, so I thought I would note that he recently had an article published on Perl.com entitled Rapid Website Development with CGI::Application, which is all about the popular and mature Perl CGI::Application framework for web applications. It’s definitely for geeky web developers like us, but shows how we’re keeping track of the latest trends and tools for efficiently creating robust web applications for our clients (and designing the logo for some of those tools too). Nice job, Mark!

I’d like to expand on one of the points in Tim Berners-Lee excellent recommendations on designing a good URL. He suggests leaving access out of the URL. An example of that would be the inclusion of “Public” in this bug tracking URL.

Tim is concerned about this primarily because URL access changes over time, causing the URL to need to change when the resource hasn’t changed.

There’s a bigger problem with putting access in URLs. In the era of web2.0, more sites are data-driven, providing different views of the same resource depending on how you access it. Commonly, an administrator may see links to edit and modify the data, while the public has fewer or no options to alter the content.

The problem comes when people try to share URLs to resource between different access groups. Instead of displaying the resource, the user may be prompted to login, since they are a different group than the one needed to view the resource. That’s somewhat silly– why block me from accessing a resource that I can see, even if it’s a bit different than what the sender sees?

Read the rest of this entry »

One of the most frequent uses of Perl in my job is to validate web-based forms. Here’s some explanation and sample code to how I do that efficiently and effectively.

Read the rest of this entry »

There’s been quite a lof interest in source control management (SCM) software since Linus Torvalds recently announced that he will no longer be using BitKeeper to manage the Linux kernel project. Related to this, kerneltrap.org has a timely survey about favorite SCM software. Sure it’s unscientific, but being skewed towards people who have some interest in large projects like the like the Linux kernel does make it more interesting. These are generally readers of kerneltrap.org, after all.

The two in the lead are no surprises: CVS and Subversion. CVS is the old heavyweight with a large mindshare. Subversion has gained popularity as a “better CVS”. Beyond these, the options get interesting because they get distributed.
Read the rest of this entry »