Since I have encountered a bunch of issues while trying to develop/optimize on the v.1.x branch of the application due to limitations of the existing plugin implementation here is some planning regarding v2.0
of the plugin.
The current v2.0 branch is using a self hosted Nancyfx instance, and Flex, I need to do a sample test application with embedio to see if it fits my needs better compared to Nancyfx.
The new plugin should be lightweight and should just expose IPC using named pipes. The data will be converted to protobuf and then will be passed to the application. All the remote service should be part of the Application instead.
[ ] - Move to http/websockets stack instead of custom socket implementation
[ ] - Create an application (tray) for the remote
[ ] - Application can open MusicBee if not running
[ ] - Plugin only exposes IPC (Named Pipes/ProtoBuf) for communication with the application
Plans for v2.0.0
Since I have encountered a bunch of issues while trying to develop/optimize on the v.1.x branch of the application due to limitations of the existing plugin implementation here is some planning regarding v2.0 of the plugin.
The current v2.0 branch is using a self hosted Nancyfx instance, and Flex, I need to do a sample test application with embedio to see if it fits my needs better compared to Nancyfx.
The new plugin should be lightweight and should just expose IPC using named pipes. The data will be converted to protobuf and then will be passed to the application. All the remote service should be part of the Application instead.