DirectPlay and non-win32 platforms
Of course a DPlay interface won''t be able to talk to a TCP interface. But you don''t expect an IPX interface to talk to a TCP interface, do you? There''s still a point to including both, don''t you think? Treat DPlay as just another transport layer. So if the Linux box doesn''t have DPlay don''t try using DPlay to connect to it, simple as that. But if you''ve got a null-modem connected to your friend''s windows box you can still use the DPlay interface to communicate.
Ah, OK, I see what you are getting at now.
I forgot that he wanted to use null modems and stuff. Why, I have no idea (does anyone even use a modem like that anymore?)
Of course, even with that solution, only Windows clients will be able to play against each other on null modems/normal modems.
IPX presents a problem, although he could use OpenPlay w/TCP/IP for LAN play.
-vince
I forgot that he wanted to use null modems and stuff. Why, I have no idea (does anyone even use a modem like that anymore?)
Of course, even with that solution, only Windows clients will be able to play against each other on null modems/normal modems.
IPX presents a problem, although he could use OpenPlay w/TCP/IP for LAN play.
-vince
Author
The suggestion by SiCrane isactually the one that I have already described in my design document, but I hoped to avoid it.
I guess it simply is not possible to get both platform and service provider independence. Such is life.
The game I am writing is not a massive multiuser game so users should be able to find other people to play with even if two different ways of communicating is possible. I think that I will go for this solution. Thanks, everybody.
B.S. Jacob Marner
Graduate Student of Computer Science, The University of Copenhagen, Denmark.
http://fp.image.dk/fpelisjac/rolemaker/
I guess it simply is not possible to get both platform and service provider independence. Such is life.
The game I am writing is not a massive multiuser game so users should be able to find other people to play with even if two different ways of communicating is possible. I think that I will go for this solution. Thanks, everybody.
B.S. Jacob Marner
Graduate Student of Computer Science, The University of Copenhagen, Denmark.
http://fp.image.dk/fpelisjac/rolemaker/
Vince, not to keep knocking you down, but why does IPX present a problem? In Linux you can program IPX with sockets, and in WinSock you you can open IPX sockets.
I think the best solution may be to write your own protocol. It shouldn''t be too hard...
/Pelle
/Pelle
Author
I do not think so. If I only wanted to use TCP/IP then you are right, but if I wnat to be service provider independant then you are not.
Writing a new protocol that works with multiple service providers is a lot of work. The connectivity API in Windows (i think it is called that) makes things easier.
Writing a new protocol that works with multiple service providers is a lot of work. The connectivity API in Windows (i think it is called that) makes things easier.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
