- Shopping Bag ( 0 items )
1. Introduction to Distributed Systems.
2. Pattern Language Overview.
3. Basic Remoting Patterns.
4. Identification Patterns.
5. Lifecycle Management Patterns.
6. Extension Patterns.
7. Extended Infrastructure Patterns.
8. Invocation Asynchrony Patterns.
9. Technology Projections.
10. .NET Remoting Technology Projection.
11. Web Services Technology Projection.
12. CORBA Technology Projection.
13. Related Concepts, Technologies, and Patterns.
Appendix: Extending AOP Frameworks for Remoting.
Posted March 10, 2005
Patterns are one of the key concepts to emerge in computing in the 90s. But if you read a typical book on patterns, the issue of remoting patterns often gets scant coverage. In many ways, as this particular book by Voelter et al makes clear, the problems can be far harder than for a software package running on one machine. At the most basic level, Remoting Errors (a pattern discussed early in the book) must always be a possibility as the communications channel between a client and a remote object can be subject to many failure modes. Then, later, there are issues of whether your object instances can be serialised into some kind of format able to be sent out over the network. You have to worry about marshalling and unmarshalling in the correct order. And the issues go on from there... C programmers of client-server applications may be familiar with many of the topics, if they used Remote Procedure Calls. So too might C++, Java and C# programmers. The book's topics recur, largely independent of the programming language chosen, because the issues are fundamental. The book gives a good coverage of .NET examples, and relatively little of J2EE. A bit more on the latter might have been good, perhaps. CORBA gets a brief discussion. Not because it has many prospects of future growth, I imagine. But probably because it still has a substantial market presence. Due to all those poor blighters in the 90s who had to code in this miserable framework. If, hopefully, you do not need to use CORBA, you should still read this chapter. It's a salutary explanation of a brittle and inferior pathway, as compared to using XML and Web Services for a distributed application.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.