JSquiggle find its way

Stomp, ActiveMQ, and Tinyline

Ever since I tried the Apache ActiveMQ, all of a sudden, the decision become easy. Actually, JSquiggle is a typical textbook pub/sub paradigm. However, most of the pub/sub tool are considered the "Enterprise" feature. They usually cost a lot of CPU cycle, memory footprint, and money.

ActiveMQ is really simple. It does not depends on any J2EE server. The installation on Mac OS X takes less than 20 minutes (unzip, drop, modify a few lines of config), and then it is up and running. The optional wire protocol, Stomp, looks quite promising to me. I'm not sure if I'm able to implement a distributed clock using Stomp (to embbed Lamport timestamp in message). I hope I could.

And then comes the great Tinyline SDK. It is really easy to use. I don't need to touch any XML parsing code, and the SVGDocument object is created. No wonder it is so popular.

JSquiggle 2 will use these light weight implementations to make things happen faster. I've been thinking of doing this rewrite for long time, but everything I feel like reinventing the wheel. Finally there are reasons I don't need to reinvent everything.

Firefox and SVG

OK, I'm slow. I just found that Firefox run SVG natively without any plug-in. All we need is to give the right xml namespace. Great job Firefox! Now its the time to include the Tinyline library into JSquiggle 2. JSquiggle is think of using Tinyline for at least three years.

ActiveMQ

In the development of JSquiggle 2, I found a great JMS implementation that does not require heavy full scale J2EE server. Apache ActiveMQ project is such an easy solution to the pub/sub communication. JSquiggle 2 is using ActiveMQ in early development phase. After the user interface is settled in, it will switch back to the original Zeroconf + Lamport timestamp implementation for J2ME Personal Profile.