Quote:
|
My only critic is the message system. The one that you had implemented in the first version of infinity (mp-xaml-experiment at svn) was much cleaner and nicer.
|
Well the reason we choose & implemented this one is the following
The first version of infinity had type-safe messaging. While this sounds nice you create a dependency at compile time between the sender and the receiver.
So if plugin A wants to receive message from plugin B then plugin A needs to know about plugin B at compile time
These dependencies are unwanted since both plugin A and plugin B can be written by 2 different 3th party developers. So if the author of plugin B creates a new verion he 'breaks' plugin A
and the author of plugin A must re compile & redistribute a new version too
By sending a generic message with meta data between plugins & core we avoid these hard-coded dependencies
and plugin A will keep working, even when there is a new version installed of plugin B
Quote:
|
Another point that I would to give my opinion is the base architecture of MP.
|
The base architecture we have now allows to write client & servers
In fact it is planned to create a MP-II server which has no graphical GUI and will serve any media
, including tv to MP-II and other clients (which do have a graphical GUI)
Frodo
Another point that I would to give my opinion is the base architecture of MP. If you are making it from scratch why not use the client/server approach? For me MP would a killer app if it was like this: