I talked with the JXTA guys for like an hour at JBossOne.  They were 
very interested in the JBossMX core with dynamic services.  I think JXTA 
could be easily plugged into JBoss, but the the best place would be a 
transport for JMS.  Where do you think it would be most useful?

-dain

Paul McLachlan wrote:

> Sun has just published an article in the JDC comparing JMS and JXTA.  
> Since they build both technologies they do not have a vested interest in 
> recommending one over the other.  Have a look at:
> 
>  
> 
> http://developer.java.sun.com/developer/technicalArticles/peer/index2.html
> 
>  
> 
> If time is constrained, just read the conclusions.  A few points to note 
> are:
> 
>  
> 
> 1. JMS is enterprise focussed, not internet focused
> 
>     * JMS communication is restricted to within a single firewall domain.
>     * JMS communication is restricted to a single transport.
>     * JMS communication requires static binding between peers.
>     * JMS does not specify security mechanisms under client control
>     * JMS is tied to Java (just like RMI is tied to Java), JXTA is
>       language and transport protocol independent
> 
> Note as well that JMS is tied to vendor implementations.  JXTA is free, 
> open source, and most importantly vendor independent.  That means that 
> one suppliers version of JXTA will always talk to another suppliers.  
> The same is not true of JMS, since it defines the messaging API and not 
> the message protocol itself.  So one suppliers JMS will not talk to 
> another suppliers JMS, so you become tied to a vendor.
> 
>  
> 
> Has anyone thought of implementing JXTA with JBoss?
> 
>  
> 
> Paul.
> 



_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to