Internet system handbook
A critical review of the notion of algorithm in computer science
CSC '93 Proceedings of the 1993 ACM conference on Computer science
JavaSpaces Principles, Patterns, and Practice
JavaSpaces Principles, Patterns, and Practice
Core JINI
The Anatomy of the Grid: Enabling Scalable Virtual Organizations
International Journal of High Performance Computing Applications
Globus® Toolkit 4, First Edition: Programming Java Services (The Morgan Kaufmann Series in Networking)
Business Process Execution Language for Web Services BPEL and BPEL4WS 2nd Edition
Business Process Execution Language for Web Services BPEL and BPEL4WS 2nd Edition
Federated Collaborations with Exertions
WETICE '08 Proceedings of the 2008 IEEE 17th Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide
Cloud Computing and SOA Convergence in Your Enterprise: A Step-by-Step Guide
Autonomic SLA Management in Federated Computing Environments
ICPPW '09 Proceedings of the 2009 International Conference on Parallel Processing Workshops
Hi-index | 0.00 |
Most enterprise computing programs are still not written in metaprogramming languages but rather composed line by line in software programming languages as they were decades ago. These programming languages are poorly suited to expressing enterprise processes targeted at complex, domain-specific and transdisciplinary problems. The current state of the art is that legacy programs and scripts can be used as programming instructions provided by dynamic service objects. New metaprograms (programs of programs) require relevant operating systems managing service objects as a virtual service metaprocessor. However, there are presently no acceptable metaprogramming methodologies to program, deploy, and dynamically federate these relevant service objects into a virtual processor securely and efficiently with fault detection and recovery. In this paper the emerging metacomputing SORCER platform with its federated method invocation and exertion-oriented programming model is contrasted with service protocol-oriented architectures (e.g., OGSA, CORBA, RMI) which limit us to one fixed wire protocol, static network configurations, and often restricts us to heavyweight containers (e.g., application servers) for hosting service objects.