WAP Reference System - Design
Observations
- C++ based WAP product design focused on performance issues
- Monolithic, much harder to add new components without redesign
- Regarded as successful project
- Erlang based WAP Reference system design focused on close relation to standard
- Reusable WAP components
- Well-defined WAP component interfaces
Conclusions
- To make components reusable it is much more important to have a modular design than a modular (object-oriented) language
- Low-level language => low-level design