It's a substantial rewrite of a big comms class, and all the dependants which use the types. It's boring code too, which is why no-one has done it yet. Not to mention you would probably need at least a spare PC in your house to test and debug your code properly. I looked it up at one point. if I've time I'll look into it some more at some point.derfmancher wrote:QUOTE (derfmancher @ Oct 20 2009, 07:32 PM) I think that would be an excellent idea. The solution to me sounds like to use a newer version of directx, or to totally change protocols.
How hard would it be to entirely remove Directplay from the code?
DirectX may no longer provide a communications layer at all. The recommendation from Microsoft is to use Windows Sockets to roll your own comms layer/class. (the justification Microsoft used for this was that Directplay was outdated, being initially designed for small scale LAN games, and the job could be done better by other means.....)
Edit: pkk posted while I was waffling and he's right - it is not totally removed, there are just no headers and library to develop with DPlay in newer versions of DirectX.
QUOTE No single word about total removal of DirectPlay on Vista.
Sorry -the correct word I should have used was deprecated.
Wwe cannot rely on it permanently
http://msdn.microsoft.com/en-us/library/bb318767(VS.85).aspx
They may be fully removed in the future, and the directplay headers and librairies are not in the SDK since Aug 07.



