h1

Case 6 – The Application Controller Pattern and Reflection

Think-Design-Write Test-Code

Requests from two clients being handled at once by one server

Requests from two clients being handled at once by one server

  • Description

In your work with the chat client and server it becomes apparent to you that if a server is going to handle many different commands that a case or if-then-else statement will become very large.  You explore options and in a discussion with a senior engineer named Jeong-Soon you are told that the Application Controller pattern may be what you should try.  You explore this pattern and decide to refactor your server to use this pattern.

Having already implemented storing messages you now decide to implement the requirement to instantly send messages received to the recipient in addition to storing them.

  • Deliverables
  1. Refactored UML state diagrams for your solution
  2. Refactored UML sequence diagrams for both your client and server solution
  3. Refactored UML class diagrams for your solution
  4. A client and server that works as described in the PRChat Development Overview document
  • Resources
  1. The Application Controller Pattern

    The Application Controller Pattern

  2. Reflection in Java Search in the page for ‘Creating New Objects’

Leave a Comment