Question #103721 on LinuxDC++ changed: https://answers.launchpad.net/linuxdcpp/+question/103721
Steven Sheehy posted a new comment: As far as design, I had a few ideas that revolve around MVC. Firstly, the daemon (controller) would need to hold all state (model). Clients (views) would obviously contain a copy of some of the state that they format to display, but they would be considered thing clients. Some of this state is already in the dcpp core, some would have to be kept elsewhere inside the controller. The controller would listen to on() events from the dcpp core, create an event and populate it using the core's datatypes, then send it to the view. Views can also send events to the controller. The tricky part is the communication between the view and the controller. Should we use some RPC library or write our own? Should the payload be binary or xml based? If it's xml it would be easier to communicate with front-ends that are in a different programming language or on a different operating system, but the tradeoff is of course that it is probably slower. The RPC libraries that I've seen for C/C++ don't seem to be supported very well. If we had something like the excellent twisted library for python or Spring in Java it would be easy. But Alas, nothing is easy in C++. -- You received this question notification because you are a member of LinuxDC++ Team, which is an answer contact for LinuxDC++. _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
