Re: [JXTA discuss] Project Proposal: TriPoint

Alex,

+1

This is definitively a key area for helping the grow
of the JXTA developer community, and lowering down the barrier
of entry to JXTA. Please sync up with the Commons
(commons.jxta.org) project, and let's make sure that we are
leveraging and learning from what other projects have done
in the past. I am glad you already mentioned all of them. It is
certainly the time to build such common infrastructure. It will
be nice to look also how we can easily integrate with an SOA WS
framework, and adding SLA support for services deployed within
a peergroup. We need also to tight this effort with IDE developer
pluggins (NetBeans, etc).

Cheers,

B.


Alex Fletcher wrote:
> All
> 
> I would like to propose the following project...
> 
> The name of the project is TriPoint and it is a
> framework for developing, deploying and managing JXTA
> enabled systems. The framework will include a
> component based design and reuse pattern that should
> evolve into a solid entry point to JXTA for both
> software developers and architects alike.
> 
> Addressed by this project will be the lack of a
> specified, consistent model for integrating JXTA into
> applications throughout their life cycle [from concept
> all the way to deprecation]. The TriPoint architecture
> will serve as a middle tier which sits between the
> JXTA protocols and applications that wish to employ
> them. This abstract layer will ease JXTA's learning
> curve by presenting high level functionality in the
> form of reusable components called JxBeans. 
> 
> JxBeans will encapsulate a consistent set of
> components/utilities [chat, data/content transfer,
> presence, etc.] that are oftentimes used within JXTA
> based systems and will expose them through a simple,
> uniform interface. It will be sufficient to understand
> how to create, deploy and manipulate the beans when
> constructing P2P systems as opposed to having to grasp
> pure JXTA concepts. This will ultimately reduce the
> time investment associated with implementing JXTA
> architectures and will lower their barrier of entry;
> enabling P2P concepts to be incorporated into systems
> without requiring an in depth knowledge of the
> protocols. 
> 
> I am fully aware that there are community members who
> have already established similiar efforts [JXTABeans,
> EZEL, JAL] and I am more than open to any thoughts,
> comments, and suggestions. But what I think separates
> this effort from similar ones is the focus on a
> specified model for handling the integration of JXTA
> into applications. TriPoint aims to not only provide a
> library or a set of objects that make programming JXTA
> apps easier but also a methodology for their usage and
> management that will also make designing and deploying
> JXTA systems simple and straight forward.
> 
> Thanking you in advance,
> 
> Alex Fletcher
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


-- 
--http://weblogs.java.net/blog/tra
"As Java implies platform independence, and XML implies language
independence, JXTA implies network independence."