we're ordering a new rackmount server at work with failover gigabit ethernet, redundant RAID drives, vast expanses of RAM, etc. to replace the old desktop machine that's currently doing our web serving.
this means that in a couple weeks when we get the new server, things will get moved around. the rackmount replaces the old server. the old server replaces my desktop machine. my desktop machine turns into an automated network backup machine, etc. IP addresses will change. DNS entries will be updated. things will move around.
with all the upheaval, i see as good a time as any to upgrade things to <a href="http://perl.apache.org/">mod_perl</a>. i've been playing with mod_perl a lot lately and have got a copy of the thraxil engine on my home machine ported to mod_perl with some new features added and ready to go. for you end users, switching to mod_perl will mostly just mean a nice speed improvement. i've also vastly improved the caching model, changed things so urls will be more userfriendly (eg, diaries will be accessible through a url like http://thraxil.org/users/anders/diary rather than http://thraxil.org/diary.pl?user=anders), and RSS feeds are in the works.
i intend to minimize the effects of the server moves on thraxil but my priorities have to be with my employer's systems. i don't expect problems, but i just thought i'd warn everyone well in advance that there may be some turbulence in a couple weeks. your reward for putting up with the changes should be a speed improvement and some nifty new features.