Summary

This chapter looked at the Faux Implementation pattern, which is useful in many practical applications, such as development and device emulation. Now that the chapter is on the verge of completion, I can pose a simple question: If a class implements the expected behavior and interface, can a concrete implementation of that class ever be a faux implementation?

Obviously, my belief is that it can. My definition of a faux implementation is simply a concrete implementation of a behavior and interface that seeks to subvert the mechanism that the component designer originally intended for you to implement.

You replaced your heavyweight subscriber with a lightweight subscriber that runs within the process of the Java application that receives requests from an event service. The mechanism used in the sample program reads data from a raw socket. The downside to this implementation is that you end up writing a lot of SOAP parsing and Web Service infrastructure by the time you have a robust, enterprise-ready subscription service.