Hey guys and gals!
This is my first blog entry. In the future, I want to provide some information about the current MP-II development progress from time to time.
MP-II global architecture
MP-II will be implemented as a client/server system. The server will manage all attached MP-II clients, their local resources (shares), some global preferences and so on. Basically, the server will contain the MediaLibrary and the recording engine for TV and other broadcasts (like radio, web-TV etc.). The server can automatically start because of upcoming recordings and shut down after it, or simply run 24/7. The client automatically connects to its homeserver on startup. It provides the user interface, as known from MP1. The client application can be closed after usage. In a singleseat setup, server and client run on the same machine and typically will start and shutdown together.
MP-II current state
MP-II did make a good progress the last year. The client infrastructure (core part) is far advanced. But almost all specific UI components like the Media and TV parts, the players etc. still need to be developed. Developers can take a look at the current MP-II state: just check out the MP-II project folder from our SVN trunk. MP-II only runs on Vista and above.
Currently, we're working on the MP-II server part.
We'll still need much time until MP-II can replace MP1, but it will become a great, stable, maintainable system which will provide many improvements compared to MP1.
Cheers,
Albert
This is my first blog entry. In the future, I want to provide some information about the current MP-II development progress from time to time.
MP-II global architecture
MP-II will be implemented as a client/server system. The server will manage all attached MP-II clients, their local resources (shares), some global preferences and so on. Basically, the server will contain the MediaLibrary and the recording engine for TV and other broadcasts (like radio, web-TV etc.). The server can automatically start because of upcoming recordings and shut down after it, or simply run 24/7. The client automatically connects to its homeserver on startup. It provides the user interface, as known from MP1. The client application can be closed after usage. In a singleseat setup, server and client run on the same machine and typically will start and shutdown together.
MP-II current state
MP-II did make a good progress the last year. The client infrastructure (core part) is far advanced. But almost all specific UI components like the Media and TV parts, the players etc. still need to be developed. Developers can take a look at the current MP-II state: just check out the MP-II project folder from our SVN trunk. MP-II only runs on Vista and above.
Currently, we're working on the MP-II server part.
We'll still need much time until MP-II can replace MP1, but it will become a great, stable, maintainable system which will provide many improvements compared to MP1.
Cheers,
Albert