Application models of distributed applications are various so that a model appropriate for an application can be inappropriate for other applications. For example, client-server model is the most generally used model for distributed applications but peer-to-peer model is more appropriate for groupware applications. Although supporting several different application model in a framework can give flexibility to design and implement distributed applications, the difference of communication type and communication entity management should be handled in consistent and uniform way.
In our distributed object system, Distributed Object Management System (DOMS), both client-server and peer-to-peer models are supported in a well combined model and the application models are supported in distributed objects level so that to design a distributed application can be flexibly done with high level abstractions and the combined model with distributed access controls can support other communication types like player-viewer model.
In this paper, the combined model to support both model in a framework and the variance of the basic models will be discussed with the design and implementation issues.