My article on Using ETags to Reduce Bandwith & Workload with Spring & Hibernate went up on InfoQ today. I'm now waiting in trepidation to see what sort of feedback it gets. Hopefully, I haven't overlooked something obvious. It was fun pulling it together, as I don't get that much of an opportunity to get hands on keyboards these days. I am thinking that if there is enough interest, I make give this open source idea that I've been hearing about a shot and create a project around it.
Update 2007-07-20: There have been a couple of good follow ups on the article:
- Bill De Hora's compares the cultural design centrers of the Spring/Hibernate (Java), Djanjo and Rails communities: "I suspect designing for the Web instead of around it is at least as important as language choice"
- Dare Obasanjo gives a nod to Bill's article by taking a back handed shot at Spring/Hibernate: "It will use a Web application development framework that enables rapid Web development which is designed for the Web as opposed to having some HTTP related features being bolted on". Dare is fooling around with a Facebook application built on AWS. Hmm... Facebook... PHP right? I wonder if that qualifies as one of those "designed for the web" thingies?