[JXTA discuss] 2.2 plan?

Henry Jen <[email protected]>
Newsgroups gmane.comp.java.jxta.devel,gmane.comp.java.jxta.general
Message-ID <1111095305.5497.12.camel__37445.0999465354$1111037781$gmane$org@hammerhead.sfbay.sun.com>
Hi,

As 2.1 is now released, we should really consider what to deliver for
next 2.2 release.

By now, there are some efforts that I am aware of:
- RDV support by Mike Duigou(bondolo), Rick Keiner(exocetrick)
- Relay support by Michal Prochazka
- UDP transport by Alexander Carôt
- XPath based discovery/APR DBM based CM by Rick Keiner

And here is a list that I would like to work on(and I am inviting the
community to get involved):
- Converting log to new logging mechanism
- Refactoring the configuration process(To be compatible with J2SE
PlatformConfig, ext::config)
- Reliable layer for BidiPipe
- Refactoring SocketTunnel & BidiPipe to allow multiple connections
- Continuous cleanup on defects reported in issue tracker

Please be noted that this is just a list in my mind, does not mean that
they will be targeted for 2.2 release(would be great if they can :-).

Besides coding, I would also like to see more documentation efforts.
Migrating existing documents to Wiki, adding n"Capri"ew design
documents. I hope we can have up-to-date document by collaborating on
the Wiki content.

What do you think should be in next release? What is the cool
application you are working on based on jxta-c? I am really interested
to know.

Oh, we should pick another codename for 2.2 release. The rule is "exotic
vacation hide-away". My proposal is Disneyland, although it is not
exotic, but hopefully the 2.2 release will make using jxta-c easy and
enjoyable experience. :-)

Cheers,
-- 
Henry Jen aka slowhog
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCOfgHLNaoAyBG0PURAk64AKCDItap0cBL2drqTSsMbPbquQdZIACeNMYg
t+/+DfniNy8ZfygFZDlPJYg=
=o/FB
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.