What's the point, where's the payoff?

I have put considerable effort into the AgileWiki and will continue to do so. Why?

Because an implementation of a Rolon is a generic first-class user object. The catch is that you will learn to think in terms of ledger, journal, classifier and descriptor. But having framed an application object in those terms, your data and inter-object relations are already implemented for you. You just add the "business logic".

That's pretty powerful. It is heads and sholders above EJB or anything else. That's why.

So why hasn't it been done before? What's wrong with EJBs and Portlets and all the rest?

First, Rolonics separates out classifiers, which define the inter-relationships. A comprehensive set of classifiers can be implemented by the container (the Ark). You just plug your application into that and turn it on, and you've just finished a big part of your application. This is a very different (and much more general) approach than is taken by any other application server.

Second is time. Most application servers break when you add some aspect of time--it is always implemented with the ledger (state), and time as structure never works except as a special case for limited problem domains. In contrast, a Rolonic system includes time as a major aspect of the overall implementation. Applications which deal with time present no difficulties to a Rolonic Application Server, like the AgileWiki.

'Nuff said!

Bill