[jarti-announce] Quick wrap up and update

[Tim P. <ti...@li...>]

Hello all,

It is almost the end of the year and I just wanted to fire off a =20
quick update and thank-you note to everyone on the mailing list.

The SimTecT conference in early June this year marked the first =20
public release of jaRTI. The response in the ensuing 6 months has =20
been well and truly beyond what I had hoped for, and the interest and =20=

support shown for the project has been amazing. As evidence of this, =20
the number of subscribers to this list has grown from 7 after the =20
initial release to 29 as of today. Thank you all for taking an =20
interest and I hope that we can continue to grow the community, and =20
through it, a viable open source RTI.

Before I move on, I would just like to quickly take the opportunity =20
to encourage everyone who uses or has tried jaRTI to **LET US KNOW!!=20
** This is especially important it you had a problem or found some =20
part of the process difficult or annoying. We need to know these =20
things to improve on them and help create a better project. Whether =20
you send an email, post on the forums, use carrier pigeon or send =20
smoke signals doesn=92t really matter, just don=92t be silent!!

I would also like to take this opportunity to put a big shout-out to =20
the co-founder of the littlebluefrog labs and co-developer of  jaRTI, =20=

Michael Fraser. His work has been invaluable and there is more to =20
come! (as I talk about below).

UPDATE

Active development continues on jaRTI-0.7, with the full release =20
expected around February next year. By a clear margin, this release =20
will be the biggest yet. Where other versions have addressed around =20
60 issues/tasks/bugs each, thus far the count for v0.7 is well over =20
100 (head over to Jira and see for yourself). Quite a lot of work!

The forthcoming version has focused primarily on improving the inner =20
structure of jaRTI to enable a simpler and more efficient framework =20
so that custom extensions are easier to develop and use. Some of the =20
features to look out for include:

*Improved performance with refactoring of JSOP bindings
*Beginning of C++ bindings
*Basic MOM support
*Full automated unit testing environment (source only)
*Numerous bug-fixes
*RTI-NG compatibility interface (java1)
*Extended console (kill federates and federations)

Never content to let a community desire go unmet, Michael has been =20
hard at work designing and implementing the beginnings of a C++ =20
binding for jaRTI. A preview release of this will be available soon.

We also have some extra special plans for documentation and =20
useability. I won=92t divulge what they are right now, but I will say =20=

that they are a little out of the norm. Keep an eye on the community =20
section of the jaRTI wiki page (top right) for information as it =20
comes to hand!

Once again, thanks to everyone who has shown an interest in jaRTI, =20
the response has been fantastic and will prove an excellent =20
foundation on which to build.

A happy new year to everyone!

Tim.