Execute what?

January 23rd, 2010

So, this is another one of my weekly updates for my CSCI networking class. I’m happy to report that I’ve made a lot of progress since last week. It’s probable that this week I’ll be finishing up the server and begin testing it on the Zion CS server. Essentially, I’ve got the project listening on the socket and spawning child processes to handle the incoming connections. As per Dr. Dan’s note, we’re not required to be able to handle concurrent connections – although that is possible in theory.

I’ve mainly avoided it because from what I understand, how different systems handle shared memory between multiple threads differs based on implementation. I figured since I was doing my original development on Mac OS X and then deploying my production copy to Zion it would be wise to keep it simple, even though they are both Unix derivatives when you get down to the bare metal.

My to do list at this point is to get the server executing files using the XBitHack (but Dr. Dan says he needs to tweak that part of the assignment, so I’m holding off on implementation) and then to get the server running as a daemon process. After that I should be done. Hip hip hooray!

Working Toward a Better MVC

June 19th, 2009

One of the latest trends in website development is that of the Model-View-Controller (or MVC) design ideology. For those individuals reading who are unfamiliar with MVC, allow me to give you the rough sketch of what it is. The idea comes from the concept of three distinct tasks of an Application:

  1. Read or Write Information from a data source.
  2. Process that information in some way.
  3. Display the processed information.

Those three tasks are at the heart of nearly every application on the market. We’re all a bunch of data manipulators! Just when you thought that your checking account had some greater significance, right? These three tasks make up the three parts of MVC. The Model is a representation and a means of communicating with your data source. The Controller is what processes your information for you. And finally, the View is what displays your information in a friendly format.

I first had the pleasure of being exposed to this via my position with the University of Georgia’s EITS. However, if you want a shining example of an artfully designed MVC Framework, the best example I’ve seen is Ruby on Rails. While Rails may singlehandedly be responsible for giving Ruby a jump into the spotlight of web development, it is not without its problems. Rails is, for example, very resource heavy if not implemented exactly right.

So, in light of my love for the ease of developing for Rails and my frustration with the fact that finding a web host who adequately supports it I have started work on developing an MVC framework that brings some of the things I love about Rails into the PHP arena. Read the rest of this entry »