Stuff Happens

• Moved /scenarios, /scripts, and /utilities to /boa/scenarios, /boa/scripts, and /boa/utilities. Parts of /misc have been moved to /boa/misc. Yeah, there'll be broken links. Better now than later.
• In case there's any other Programmer's Notepad fans out there, I've made an AvernumScript scheme. Being able to whip up lexers for small, special purpose languages is probably Programmer's Notepad biggest strength. So you'd think it would be better documented. C'mon Simon, even an XML schema definition for .scheme and .schemedef files would've helped.
• I've set things up so I can host Subversion repositories here. You can access the web interface at /svn. At the moment, I'm the only who can write to it (through SSH), but go nuts if you want to view it. Not much on it right now, but from now on anything that I put on this site will be developed on there.

Project Darkstar

The last couple of days I've been playing with the Sun Gaming Server (or Project Darkstar). Aside from a few gotchas, it's pretty intuitive. In a short span of time (probably well under eight hours if I had been working on things straight and not changed my mind halfway through) I was able to whip up a server and client for a simple game. That includes learning as I went. The server doesn't seem to want to set up the database here (Darkstar uses Berkeley DB), so it seems the world will never get to play Rock Paper Scissors Online. Oh well. Following are my impressions at first blush.

• Server side, everything is Java. State is persisted through Plain Old Java Objects that implement the ManagedObject interface. Such objects are serialized and kept in a Berkeley DB. Yeah, serialized. I guess the name of the game is getting your model right on the first try, so you don't have to wipe your database six months down the road. ManagedObjects keep a ManagedReference to other ManagedObjects (they can't directly refer to one, or they'd just serialize a stale copy along with their own state when they get saved). Haven't looked at the source, but I'm guessing ManagedReferences are just UUIDs for primary keys along with generics to make life easier. The whole system is a bit annoying to use, until you remember that your using a piece of software that appears mono-threaded but is actually multi-threaded, able to run on multiple JVMs, and accesses a database behind the scenes. Kudos to the team for letting people write servers without reinventing the concurrency wheel, or the database tier wheel, or the communication wheel. The only major issue is lack of garbage collection on ManagedObjects (they are stored in a database, after all). Could turn some Java programmers off, though it might be possible to write a Task that performs a garbage collection on the database periodically.
• Darkstar seems to solely use Berkeley DB. I can see people in the near future writing extensions to let Darkstar use all sorts of free or proprietary databases. Hey, if you already own an Oracle licence, you might as well use it.
• Unlike the server, clients can be in any language. The client APIs at the moment are in Java and C. Communication between the server and the clients are done with byte arrays, and thus can be language independant (though if you only want Java clients, I guess there's nothing stopping you from serializing communication objects). In a way, I wish Sun would have made all communication with XML, and had the Java API use Documents for communication. I understand what they did was for generality and performance reasons, but another useful extension would be making XML communication a breeze. From the initial projects I see right now, communication is done through serialized Strings, which is fine for whipping up a MUD, but not for a game of decent complexity.
• The client API is event-driven, which makes writing a traditional MUD difficult. I tried making my client run off the terminal at first, but then gave up and began to use Swing. A cleaner client API for those who want to write MUDs (all communication with Strings, blocking I/O, etc.) would also be great.
• Finally, I don't think Darkstar is just a game server. You have this great framework for dealing with persistent objects on a server that can span multiple machines, with the ability to connect to an arbitrary number of client machines. This doesn't have to just be gaming software (to pick an example, Sun's Project Wonderland is built off of Darkstar). By the same stroke, Darkstar is too generic to be immediately used to build games. There will be the need for a role-playing framework, a first-person-shooter framework, and so on.

Pretty interesting stuff. Might give me something to do for the next little while. Summer activities are slowing down, and I'm beginning to feel the absence of homework.

The 'c' in filectime() doesn't stand for create.

Who knew? Anyway, no content, but I'm having fun learning CSS.

ANT! BERKELEY DB! IVY! JIRA! NETBEANS! SOAP! TOMCAT! XML-RPC!

Otherwise known as: I started work this Monday. A steep learning curve, but I haven't gone crazy. Yet. In light of recent events on Shadow Vale, I have ceased the strenuous work on my unfinished scenario, and produced another. You can find it here. Remember, always take my scenarios as seriously as they deserve to be.

Hello World

Don't let the new layout fool you. There still is nothing on this site. Hopefully, that won't last long, but don't get your hopes up. Right now, I'm just playing around with PHP. I didn't do much refactoring, and most links should still work. /developing/ moved under /scenarios/, and both /dikistats/ and /dumps/ moved under /misc/ (if for some strange reason you need access to those things).