Reply to thread

Message

<blockquote data-quote="misterd" data-source="post: 129099" data-attributes="member: 19503">Hi,I would prefer that we should first try to combine Admirals or Maschines test app with hevea or something like that. This could make things easier, if we know that this approach will work.I suggest to use the SVN of the old webinterface or the one for mp-plugins. Too many SVNs make everything more complicated.I thought that it would be better if we separate between the web application/service and the back-end systems. The reason is that if there is a modification or technique change in one of the back-end systems, we only have to modify this abstraction layer. The layer should be very simple and more like a wrapper. If we would support TVEngine2 than it would be possible to create such a class hierachie:- SimpleMPClient (Representing a client without TV)- ClientWithTVEngine2 : SimpleClient (Client with TVEngine2)- ClientWithTVEngine3 : SimpleClient (Client with TVEngine3)- Server (Generall abstract class for a server. Will access db and tv service)- MasterServer : Server- SlaveServer : ServerThis is just an example and not a final version. The final version can only be declared when we have a feature list and a deep look into the sources of MP and TVServer. My proposed web service than would be very similar to this abstraction layer. Another advantage that if there is the need for a different web service or something else, we have a simple global interface which will wrap the whole back-end systems. I hope that this is detailed enough for everyone.Regards,MisterD</blockquote>

[QUOTE="misterd, post: 129099, member: 19503"] Hi, I would prefer that we should first try to combine Admirals or Maschines test app with hevea or something like that. This could make things easier, if we know that this approach will work. I suggest to use the SVN of the old webinterface or the one for mp-plugins. Too many SVNs make everything more complicated. I thought that it would be better if we separate between the web application/service and the back-end systems. The reason is that if there is a modification or technique change in one of the back-end systems, we only have to modify this abstraction layer. The layer should be very simple and more like a wrapper. If we would support TVEngine2 than it would be possible to create such a class hierachie: - SimpleMPClient (Representing a client without TV) - ClientWithTVEngine2 : SimpleClient (Client with TVEngine2) - ClientWithTVEngine3 : SimpleClient (Client with TVEngine3) - Server (Generall abstract class for a server. Will access db and tv service) - MasterServer : Server - SlaveServer : Server This is just an example and not a final version. The final version can only be declared when we have a feature list and a deep look into the sources of MP and TVServer. My proposed web service than would be very similar to this abstraction layer. Another advantage that if there is the need for a different web service or something else, we have a simple global interface which will wrap the whole back-end systems. I hope that this is detailed enough for everyone. Regards, MisterD [/QUOTE]

Verification