OK, so I just released Beta2. We need to decide what else, if anything, we need to add before releasing 3.0.0.GA. Right now we've got: * Basic protocol (intended to be a model for implementations, not for primary usage) * Multiplex protocol (this will be the basis of JRPP which is multiplex + SSH + some option negotiation protocol) * A complete discovery API, but no (production-grade) mechanisms yet * Transporters, at least on a basic level (I can envision many more features to add, but this isn't a priority for us) * A complete streaming API (via JBoss Marshalling), but no (production-grade) mechanisms yet Things that are currently scheduled for 3.1 or later and for the supporting projects: * SSH + negotiation protocol to round out the multiplex transport * Discovery mechanism based on SLP (RFC 2608) implementation (this is has an SLP component and a Remoting component) * Streaming mechanisms for Multiplex+SSH * Maybe some generic streaming mechanisms for streaming directly over TCP? * Protocol compatibility layer for older Remoting wire protocols * Discovery mechanism based on JGroups (?) * An improved standalone API to make simple clients and servers be very easy to write * Remoting MC integration * Strategy for creating EJB2, EJB3, Remote JMX, Remote JDBC, Remote JNDI etc. services, including addressing compatibility Inclusion into JBossAS hinges on most (if not all) of the future scheduled tasks being complete as well. What do you guys think? Is 3.0 production ready? Is there a target audience for it as it is right now? I'm inclined to put it out there more or less as it is now, personally, and get a move on the other features I've listed for 3.1, locking in to a 12- or 16-week release cycle. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197501#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...