0 Members and 1 Guest are viewing this topic.
The only way around this problem is to axe the ability for WinMX (the default clients) from being able to go Primary on the network. And instead have the new clients take over the Primary job and also setup some kind of new client that is just a network node. A type of advanced dummy primary peer that we can setup on a few dedicated servers which hold hundreds of secondary peers. This is the only way we can allow both WinMX (old clients) and new Enhanced clients with Enhanced protocols to coexsist on the same network.
He has also thought about another way we could do an enhanced client within WPN. And that would be by delivering an updated version of the Eagle Patch which when run on a WinMX client that is running as Primary will intercept certain packets from clients running the enhanced protocol and able to forward those on to other enhanced clients and WinMX primaries (which are also running the updated patch). The other alternative he thought of was to have us update our Peer Cache software to dish out primaries to Enhanced clients that support the enhanced protocol while still dishing out normal winmx clients to other normal winmx primary peers.