jBouncer: A Java IRC Bouncer (Proxy)

Sometimes you want to be connected to an IRC server all the time, even when you're not.

In that case you need an IRC proxy, or bouncer, that will stay connected to the IRC server(s) all the time.

That's what jBouncer does.

JBouncer is a Java implementation of a simple IRC proxy (sometimes known as an IRC bouncer). It can run on Windows, Unix, Linux, etc.

An IRC proxy is a program that connects to any number of IRC servers. You can then use an IRC client to connect to the proxy and use those servers. When you disconnect your client, the proxy stays connected to the IRC server.

Rasmus: "I don't like SOAP"

At the PHP Forum in Paris this year, Rasmus Lerdorf (the creator of PHP) wittily explained that SOAP was "intrinsically broken" because it's too complex... "just as anything that takes more than 20 minutes to understand".

I liked the way he put that! ;)

When it comes to webservices, I myself tend to prefer XML-RPC (which goes by the motto: "Does distributed computing have to be any harder than this? I don't think so.")... Sometimes, I also wonder if REST would be a nice alternative...

Inside the iPod nano

Wanna look inside your iPod nano? This guy does it right in front of your eyes!

PHP: why use DOM/XML writer functions?

There's one thing I was wondering about: why would you actually want to use the DOM/XML writing functions of PHP to generate XML? I mean: we've been generating HTML without specific functions for over 10 years, so why would we need a library to build a DOM tree instead of outputting XML directly??

Well... I got an answer at PHP Forum: it makes sure your XML is well formed when you spit it out!

Ha! I could have thought about that!

Now I'm wondering if I should be using this as a replacement for echo in order to make sure I generate well formed XHTML all the time... ;) I mean... generating a DOM tree would be overkill, but generating the XHTML code on the fly with XMLwriter might actually work out pretty well...

Hum...

Status of PHP 5

Here are a few bits of information I collected at PHP Forum (Nov 9 & 10, 2005):

  • It is estimated than no more than 5% of the servers running PHP have switched to PHP 5 yet
  • PHP 5.0 is a feature release, not a performance release. Therefore it is slower than PHP 4.x. Therefore it makes no sense running apps designed for PHP 4 on PHP 5.0.
  • PHP 5.1 should almost match the performance of PHP 4.4
  • Rasmus will probably migrate Yahoo's servers from PHP 4 to PHP 5 once PHP 5.1 has undergone a few weeks without any major issue.
  • It is extremely painful for everyone to make code that works on PHP 5 as well as PHP 4, especially because you cannot redefine the clone statement in PHP 4 for compatibility.

Okay, that's all I can recall right now! :P