search

marceldev89 / BattleNET

BattlEye Protocol Library and Client
GNU Lesser General Public License v3.0
76 stars 44 forks source link

Connections with multiple servers doesn't work as it should #17

Closed marceldev89 closed 11 years ago

marceldev89 commented 11 years ago

Or at least that's what people have been telling me in the past. If this is still true, I'll fix it. :)

st4l commented 11 years ago

Multiple servers at the same time? If they are using separate entities of beClient there shouldn't be a problem, there's nothing static in it. The only problem I can think of is the thread.sleep(500) in the main loop, and THAT can be fixed if they spawn a thread for each beClient instance (and server), as far as I can tell beClient is thread safe (it doesn't access memory areas outside of the instance)

marceldev89 commented 11 years ago

I've been told a while back that sometimes messages from one server would end up at the client connected to another server. But it seems odd to me as well since it's bound to ports setup during connection.

st4l commented 11 years ago

Yup, sounds like a PICNIC problem to me.

marceldev89 commented 11 years ago

lol

I'll leave it here just in case someone pops up with a reproducible case. :)