why yes, of course we have velociraptors

A friend of mine recently decided that she was going to built herself a new computer. Inspired by this I got up off my highly apathetic ass, and started planning my new computer. Since my current desktop is named Carthage, I thought Carthage 2.0 would be a fitting name for the project. So far the plan is to get the most power for my incredibly tight budget. This means spending the time to hunt down deals on newegg and other websites like it. So far I have purchased one part. That part is the XCLIO Windtunnel Fully Black Finish 1.0 mm SECC Chassis ATX Full Tower Computer Case. There was a special sale on newegg which dropped the price to 80 bucks so I snatched it up. I must say it is a brilliant case, everything just works. Today I locked myself in my room and transfered the parts from Carthage 1.0 into the new case. Damn it looks sexy. Depending on my next paycheck I hope to buy the next part.

Here is a link to the Gallery hosting pictures of the Carthage 2.0 project: [Carthage 2.0]

After the presentation i actually went to town working on the system. So far the results are promising and yet discouraging at the same time. At this point in time the server would appear to be (almost) sully functional. However due to some client side issues (and possibly one or two server side issues) things are failing miserably. Right now it is possible to retrieve simple webpages. This would be good but these simple pages are lacking elements such as pictures, proper formatting, etc. I am attempting to narrow down the possible locations this bug could be but it is slow going. I believe it is in the server side handling of multiple requests but I am not entirely sure. Today I decided to redesign how the server and the client handle requests. I am pretty sure that once i revision this section and then rewrite it a good portion of the problems will disappear. The current setup has one main client thread handle the connections from the browser. This main thread then spawns two I/O threads which handle input and output from the website, the browser, and the server. This section is pretty solid and I am not sure i will have to change much there. The server on the other hand will have to undergo large changes. The server, much like the client has one main thread to handle connections from  clients. Also like the client this thread then spawns threads to handle input and output. This is where things are getting messy. These threads are a tad bit confusing and don’t do everything they should so they will be rewritten to avoid the problems I am currently having. So, I guess thats all the important stuff about the proxy. I think i will also mention the idea I had while riding a bus back home today: I decided I could create a program that determines the fast route from point A to point B in my school. It does not have a “huge” inpact on anything but I think it will be a neat project to undertake when I finish the proxy or get fed up with the proxy.

So I guess thats all.