XML Design Patterns

-

Christopher Alexander:

Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice

Why?

• Better and faster communication with those who know patterns.
• Most of the time complex problems are solved by a mix of basic patterns, which would have been tricky to find and understand without knowing the patterns behind it
• All developers know and understand the same catalog of standard patterns, under common names
• a solution to a type of problem is thought out once and can be coded easily, errors will show up earlier and therefore coding speed and quality rises.
• help by giving ideas on how to solve a problem, and giving extra forsight about consequences.
• programs are:
  - easier to maintain
  - easier to understand for other developers
  - A clean seperation between GUI and implementation is almost a side effect

There are two kinds of XML DP:

- XML-related

- grammar-oriented

Also, there are applications of traditional DP, and XML-specific DP.

• Command DP
• Flyweight DP
• Iterator DP
• Mediator DP
• XMLable DP
• Self Documenting Files
• Multi Part Files