Advanced Collaboration Grids

Grid computing technologies enable wide-spread sharing and coordinated use of network resources. Among the number of types of grids collaboration grid takes a significant attention from the researchers and communities. But so far collaboration has not been used in a consistence fashion by different communities. Hence identifying the issues related to grid collaboration and finding some open standard approaches to overcome these obstacles is much needed. These approaches can be different from each. But what important is that these approaches should follow open standards that can be agreed and used by every interested parties. Taking this matter into account I thought to open this tread to address the above matters.

Collaboration become regular and important in the grid paradigm. But so far collaboration has not been used in a consistence fashion by different communities for many reasons. Hence Identifying the related issues with the collaboration has become one of major concern among research communities for last couple of year. The challenge is to finding an open standard that can be agreed by every communities.

A grid is basically built on services. In other words a grid is a better example for Service Oriented Architecture(SOA). These services are at each separate layers in the grid architecture according to their functionality. Approaching to the concept of collaboration in the current grid services hierarchy collaboration can also be identified to a set of services. Therefore implementing a service based middleware to handle the the concurrent events coming from grid participants is quite natural. The same kind of implementation has been done by Indiana university but again its a shared event model using common message broker. They have proved the concept instantiating that model that enable working concurrently on a single OpenOffice files by many peers from any corner of the world. But the problem I see in this is the solution is application specific and so no common interface provided that can be used commonly. Therefore I believe that extending this concept to model a Service Based middleware instead of it's shared event based model that would be a more flexible in general.