Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Object-oriented application frameworks
Communications of the ACM
Microsoft .Net Remoting
Web Services Interaction Models, Part 1: Current Practice
IEEE Internet Computing
Architectural styles and the design of network-based software architectures
Architectural styles and the design of network-based software architectures
A distributed object model for the javaTM system
COOTS'96 Proceedings of the 2nd conference on USENIX Conference on Object-Oriented Technologies (COOTS) - Volume 2
International Journal of Parallel Programming
| Hi-index | 0.00 |
Programming languages rely on type systems to safeguard the correctness of a program. In existing technologies, types defined in a program are meaningful only within its runtime, so the definition of a remote resource must be obtained and verified to ensure a correct and type-safe interaction. However, obtaining a consistent meaning of a resource in a distributed environment requires much human effort and coordination, thus making the development process difficult to scale to an Internet-like open environment. The key lies in the lack of a truly global naming scheme to unambiguously and automatically resolve programmatic types in the Internet. In light of this, we propose Uniform Type Locator (UTL), a worldwide scope type naming scheme. We also design and implement a new strongly typed object-oriented programming language called Meso to natively support UTLs, and a protocol to facilitate program interoperations. We illustrate through examples how Meso can be used to make developing applications in an Internet-like open environment as easy and type-safe as developing them in a single runtime environment.