Reply to thread

Message

<blockquote data-quote="Mike Lowrey" data-source="post: 682206" data-attributes="member: 88236">@KoenZomersIt's only needed for mobile devices and should not be part of the service itself!That's why i questioned how it should be implemented.For MPCC you have to look on cheezys IPIMP code... [USER=56421]DieBagger[/USER]Looks also interesting, but cheezys MPCC already has two-way communication... The main question is whether we put different architectures for the services together or should really consolidate them <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />If the last has more supporters we should talk to cheezy <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />THat really good, i think you have better connections to change infinityloops position <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="Mike Lowrey, post: 682206, member: 88236"] @KoenZomers It's only needed for mobile devices and should not be part of the service itself! That's why i questioned how it should be implemented. For MPCC you have to look on cheezys IPIMP code... [USER=56421]DieBagger[/USER] Looks also interesting, but cheezys MPCC already has two-way communication... The main question is whether we put different architectures for the services together or should really consolidate them ;) If the last has more supporters we should talk to cheezy :D THat really good, i think you have better connections to change infinityloops position ;) [/QUOTE]

Verification