Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 128670" data-attributes="member: 10347">Alright, just to keep the momentum going, I've just completed the client discovery code for the ECP2 plugin. This means that any program can send a standard UDP multicast and all MP clients with ECP2 loaded will respond. The program can then use this info and use ECP2 to connect to and control a particular client. I'll be updating the web service soon to make sure its client/server config ready too. Changes in SVN if interested.While I was doing this, I was wondering what we'll do with TVEngine2 support. Given the different nature and different structure between the old and the new TV engines, do we attempt a solution that works with both, or go with the newer one only...I've also attempted to gather info and the consensus from this thread and put all that into a nice graphic for those who hate reading long blocks of text. This is the current plan, but still in its early stages. Let me know what you think, suggestions, criticisms etc. here, and I'll update it as we go along until we get a general consensus on most things. (I'm a big fan of diagrams and pictures - makes things much easier and quicker to digest I reckon.)I am doing this at 1am btw, so if bits don't make sense its probably not you <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />. Without further ado, <img src="http://www.gliffy.com/pubdoc/1167188/L.jpg" alt="" class="fr-fic fr-dii fr-draggable " style="" />Sam</blockquote>

[QUOTE="samuel337, post: 128670, member: 10347"] Alright, just to keep the momentum going, I've just completed the client discovery code for the ECP2 plugin. This means that any program can send a standard UDP multicast and all MP clients with ECP2 loaded will respond. The program can then use this info and use ECP2 to connect to and control a particular client. I'll be updating the web service soon to make sure its client/server config ready too. Changes in SVN if interested. While I was doing this, I was wondering what we'll do with TVEngine2 support. Given the different nature and different structure between the old and the new TV engines, do we attempt a solution that works with both, or go with the newer one only... I've also attempted to gather info and the consensus from this thread and put all that into a nice graphic for those who hate reading long blocks of text. This is the current plan, but still in its early stages. Let me know what you think, suggestions, criticisms etc. here, and I'll update it as we go along until we get a general consensus on most things. (I'm a big fan of diagrams and pictures - makes things much easier and quicker to digest I reckon.) I am doing this at 1am btw, so if bits don't make sense its probably not you ;). Without further ado, [IMG]http://www.gliffy.com/pubdoc/1167188/L.jpg[/IMG] Sam [/QUOTE]

Verification