Mike's face
Monday, December 17th, 2018








HOP Server

Photo of HOP Server

A straightforward, easy to learn and understand, productive webserver with programmable features for the purpose of creating dynamic websites.  Simpler than J2EE, better organized than PHP, and more productive and efficient than both.

Configuration data, web pages, web scripts, data persistence, is all managed through the HOP system.

At one point, I was successfully serving two data driven websites for actual paying clients, using an early implementation of my Java server.  A surprise, but eye opening PHP based project distracted me from my Java server a while ago, and since, I've been using PHP for quick dynamic website solutions.  I had to create a whole foundation of functions including data persistence and template management, and eventually, it got pretty smooth.  PHP has been fun, but I miss my previous Java/JavaScript/XML Java server.

I also had a paying client running on a J2EE JBoss solution.  Other J2EE experiences in other workplaces have also been interesting, and successful.  But I know from experience that life can and should be better.  If you're in a development shop, you've seen it.  How many developers do you need to manage your average JBoss / Weblogic / Websphere / EJB / Hibernate spiel?  How do the developers spend their day, how much do they produce, and how much time is lost in recompiling, redeploying, reconfiguring, and finding bugs?... right...  If you want to hire me for a J2EE project, great!  I know all kinds of things to make it work efficiently.  But not everyone has this kind of expertise available.  I think it should be possible for someone to provide a different method of writing these kind of projects, so that less Jedi-knight-level experts are needed.

I'd like to have multiple releases, one that makes it easy for a developer to create simple mom-pop-shop dynamic websites (no less capable than the usual php based website), and another that provides enough flexibility to use it for large projects like a newspaper or a bank.  The "enterprise" version obviously needs things like scalability and redundancy.


(C) Copyright 2004-2007 Mike Pot