Note: is in rebuild. Please accept my apologies for broken links, missing stuff, etcetera - more

When Andrew Santosusso, newsletter editor, asked me whether I wanted to write this newsletter, my first reaction was "this guy must be desperate to ask me." Still, as I like writing and like to think I'm decent at it, I gave the offer some consideration. Would I be good enough to meet your, the reader's, standards? Is it possible to come up with reasonable topics week in, week out, about "Jini"? Is this going to interfere with my regular job?

After answering with three times "yes", I decided to take the plunge. Part of my regular job involves learning about technology, and my experience is that writing about stuff is actually a great way to learn about it.

This is my first of a hopefully long series of newsletters dedicated to the topic of Sun's Jini Connection Technology. As I think it is polite to introduce oneself before starting to talk to a large audience, this one is about myself. I assure you, it will be the last one on this topic.

The first time I heard about Jini was when the technology was introduced at the end of 1998. I am the CTO of Acriter, a young software company, and we were looking for something that could function as the "infrastructure" for the application we had started to build. We were burnt by off-the-shelf application server products as a consulting company, so we didn't want to go that route as an ISV. Enterprise JavaBeans was brewing, but the standard was lacking and clean, small, easily interchangable EJB containers were not available. We were about to decide to build our own, when the Jini announcement came.

The various parts of the Jini technology seemed to provide just the bit of infrastructure that we needed, apart from a bit of database interfacing - our company's idea is to build software as services, and Jini perfectly fitted that vision; often, shared vision is more important than bits of technology. So, we struck the EJB idea and set out to build a distributed application server on top of Jini.

As we more-or-less based our company on Jini, we thought it advantageous to become an active member of the Jini community. Since March, I am so lucky to be a member of the community's first Technology Oversight Committee, a great opportunity to help shape this community. It is a new technology coupled to a new community model, and it is very nice to be able to play such an active role in this area.

So, that's the short story on this newsletter writer. Let me close this first one by asking you for your help: I don't know you, so I am guessing at what you want to hear. Educate me. Give me feedback, ask me to write about certain topics, flame me when I'm talking nonsense. My email address is Thank you for your cooperation.



Copyright (C)2000-2011 Cees de Groot -- All rights reserved.