Actually, I have tried jabberd/ejabberd before but it's mostly the full reliance on having everything set up in maldocumented config files and having to set up individual module processes with their own config files and requirements. This is one piece that had me attracted to openfire in the first place was the extremely intuitive setup/configuration/administration process. Just launch the app and log in to the web interface and go from there. But it's reliance on the memory hog known as java is starting to get under my skin. Who knows, maybe I'll make an attempt at getting jabberd set up again.

Memory-wise, I'm pretty much at my limit with this particular machine. Yes, I know it's old and I'm probably due to hand it over to a much more capable box soon. For the moment though, it handles all the other applications I run just fine.

As for GCJ: That may have been it, I'm not sure. Though it does look promising. My only concern is something like openfire wouldn't be a straight 'compile-to-binary' in the sense of what GCJ does without some form of rewriting of the program.

Thanks though.