Federated assembly -> Work so far

[Meeraj Kunnumpurath <M....@voca.com>]

Hi,
 
I have been working on the stuff around federated assembly and enabling
distributed SCA domains. Here is a quick summary of what has been done
so far,
 
Work in progress

*	Discovery Service

	*	Provides the low-level communication abstraction for
enabling runtimes participating in the domain to exchange information
	*	The abstraction supports directed message delivery to a
given runtime, asynchronous message reception and broadcast to all
runtimes participating in the domain
	*	To start with we are following a model, where one
runtime in the domain assumes the master role and is responsible for
managing the logical assembly
	*	This runtime creates the physical artifacts and
trensport them to the target slave runtimes
	*	The discovery abstraction is defined in SPI
	*	There are two implementations in runtime/services - JXTA
and Bonjour
	*	JXTA implementaion is getting pretty much there, it
mainly uses the JXTA Peer Discovery protocol (PDP) and Peer Resolver
Protocol (PRP)

*	Marshalling Framework

	*	This is similar to our loader framework, however
supports bi-directional marshalling and unmarshalling of physical model
objects
	*	This framework is used by the assembly service to
serialize and transport physical model information to slave runtimes
using the discovery services
	*	On the receiving end the serialized information is
unmarshalled by the federated deployer for being applied to the slave
runtime
	*	The abstraction is defined in SPI
	*	I am working on an implementation in core
	*	The framework supports versioning of physicla model
objects if the participating runtimes are at different versions

*	Federated Deployer

	*	This is similar to the local deployer, however registers
itself with the discovery service for receiving physical model updates
	*	The federated deployer doesn't use the loader framework 
	*	The federated deployer accepts serialized physical model
information in XML, rather than raw SCDL as with local deployer
	*	It uses the current builder framework to build, prepare
and start the components

Work outstanding

*	Define the physical model in Java
*	Define the corresponding XML infoset

Some of this is related to the contribution and assembly service which
Jeremy is working on. I assume the assembly service will be the main
consumer to the discovery service and marshalling framework on the
master side. On the slave side, the federated deployer will be
registered with the discovery service for receiving asynchronous model
updates from the master.
 
Ta
Meeraj


*****************************************************

    You can find us at www.voca.com

*****************************************************
This communication is confidential and intended for 
the exclusive use of the addressee only. You should 
not disclose its contents to any other person.
If you are not the intended recipient please notify 
the sender named above immediately.

Registered in England, No 1023742,
Registered Office: Voca Limited
Drake House, Three Rivers Court,
Homestead Road, Rickmansworth,
Hertfordshire, WD3 1FX


This message has been checked for all email viruses by MessageLabs.