Re: [JXTA discuss] Project Proposal: JXTA-Ruby - JXTA for Ruby in Constrained Environments

Hi Henry,

What we need to discuss is how the software process should be done for
this project. The way I am seeing it, we have two separate
subprojects, the infrastructure level and the application level. The
application level API should be simple and not have much of a concept
of pipes or protocols. It just has message senders, content receivers,
etc. The infrastructure API allows more control for developers who
understand JXTA.

I follow the RUP process for most projects because it results in a
good domain model and traceability. I have not seen as much benefit,
however, employing RUP for infrastructure design. We should break this
up into two groups and then have an integration effort where we use
the infrastructure API to implement the application API. Thoughts?

Regards,
Shane


On 8/3/05, Henry Jen <[email protected]> wrote:
> Shane Isbell wrote:
> > This goal of this project is to provide a Ruby API for the JXTA
> > protocols. A key requirement of this project is that JXTA Ruby needs
> > to run within constrained environments (handsets). To achieve this, we
> > will bind Ruby to the jxta-c implementation This will limit key
> > aspects of JXTA such as dynamic loading of code but will allow the
> > Ruby developer to develop P2P based mobile applications on the JXTA
> > platform.
> >
> > I am proposing this under the core project category.
> >
> 
> +1
> 
> Cheers,
> Henry
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
>