Oct 2, Go for a New Architecture

After reading and analysis, I found some problems existing in the current middleware:

1. It does not support all the requirements.
2. the middleware mechanism is not reasonable. Applications instantiates the middleware. How to make sure we run several applications simultaneously but only one middleware instance? The appropriate way could be the middleware instantiates the applications, manage a branch of applications, and has a browser -like user interface.
   
3. It is not flexible. SIMS is a research project, the theoretical part is continually developing, bringing changes to implementation. For example, how to find a compatible player when joining a service is still discussing. From a developer 's perspective, what I can do is to architecture the software well to deal with the changes.
4. Integration in SIMS project is also a big problem. We have 7 partners in the project. The overall SIMS architecture for runtime applications is still not clear. To make well-designed middleware is also a contribution to the overall architecture.
   

I decided to re-architecture and build the middleware again. Only keep some design from the previous versions, but abandon all the code, both server and client side thoroughly.

At the same time, I have found what I can really contribute to this project and decided to change my thesis topic to a more challenging one!