Exploring the Faux Implementation Pattern

  • Paul B. Monday


The past several chapters have assumed that a client of the EventService Web Service will deploy their subscriber to a full Web Service environment to subscribe to a few events. In many ways, this is like using a mainframe to play your MP3 files. Not only do you waste the full potential of the environment, you introduce a whole host of unnecessary issues, especially if you have a small client. In the case study, for example, you deploy Apache Tomcat and the Apache Axis environment to subscribe to an event. You then build and deploy a Web Service that uses the Connector pattern from Chapter 13, “Exploring the Physical Tiers Pattern,” to ensure that the application can receive events from the client-side Web tier. This is a lot of work for little return.


Connector Pattern Simple Object Access Protocol Real Implementation Game Console Event Service 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Additional Reading

  1. •.
    Fowler, Martin et. al. Patterns of Enterprise Application Architecture. Addison-Wesley, 2002.Google Scholar
  2. •.
    Gamma, Erich et. al. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, 1995.Google Scholar

Copyright information

© Paul B. Monday 2003

Authors and Affiliations

  • Paul B. Monday

There are no affiliations available

Personalised recommendations