Hi everybody!
Has anyone seen an small enet example, or a good tutorial about it? I tried to make a small console app (based on the code snippets from the enet page), which connects a client with a server. But I faild, because I don't get a connection. The only example I got was from NFS42, but it seems after compiling it, it doesn't work anymore (no connection). Although the exe I got from him works without any problems.
I searched more than 2 hours on the net and couldn't find any tutorials or other examples about enet! Maybe you know any tutorials or examples?

Thanks for your help!

Dark_Samurai

Hi Dark,

there was a typo in one line, sorry for this
change
Code:

---

        // connect to server:
        enet_address_set_host (&address, argv[2]);

---

to
Code:

---

        // connect to server:
        enet_address_set_host (&address, argv[3]);

---

download zip

Thanks for your help, now it works!

I have another small problem:
Client1 wants to send something only to Client2. So he needs the peer of Client2, but how can I get this? I thought about sending it, but it looks like I can't send structs, or am I wrong?

Thanks for your help!

Dark_Samurai

for peer to peer connections you need a sender (enet client) AND a listener (enet server) in every game client app.

So you mean that the Client always sends his message to the server, and the server sends it to the other Client(s)?

Dark_Samurai

no, that's a true client/server model

for peer to peer every client must accept requested connections from any other client. so every game client works as a non-dedicated server running also as client.

GSTNet is client/server, so there is no possibilty for a client to connect to another client. all transfer is managed by the server.

http://de.wikipedia.org/wiki/Peer_to_peer

But why do you use a real client/server model for GSTNet?
Wouldn't it need less data transfer if you can send something directly to a Client instead of sending it to the server and then to the other Clients?

Dark_Samurai

Oi, there's a whole issue with peer-to-peer and server/client.

Mostly, with peer-to-peer it's impossible to stop the clients from just sending whatever packets they want (this is what made it so hard to stop the hacks in Diablo2).

In a pure client/server architecture, the client checks and OKs everything. There is much less probability for cheating.

Also, in a peer-to-peer, if a player enters with a shitty connection, he will be sending out late packets to everyone and generally getting away with murder. He can shoot at everyone and hit them on his screen, send out the packet, the client would then have to determine if he was at xyz location at t time etc etc.

big nightmare.

Much better to just have:

clientA sendshotpacket @locxyz;
server recieves packet
server checks if clientB gets hit;
server returns yes/no packet;

Ok, thanks for answering!

Dark_Samurai

Also, peer to peer scales exponentially, which client/server doesn't.

(peer to peer has to send data to everyone connected...which means individual clients must have HUGE internet pipes...instead of just one central server with a huge pipe.)