Skip to content
This repository has been archived by the owner on Jul 29, 2020. It is now read-only.

Hi, Seungmo Koo #5

Open
balannarcis96 opened this issue Mar 2, 2019 · 0 comments
Open

Hi, Seungmo Koo #5

balannarcis96 opened this issue Mar 2, 2019 · 0 comments

Comments

@balannarcis96
Copy link

balannarcis96 commented Mar 2, 2019

Hi,
I'm sorry to contact you like this, i just cant find any of your contact data.
I saw this old post [http://bowling-bash.blogspot.com/2012/06/teras-free-targetting-combat-server.html] of TERA's server architecture where you answered some question on the world server's architecture.

As you guys used the symmetric worker-threads approach with the world replica in each worker (TLS),
-How did you handled the concurrency problems? like if one player generates movement packets the world server is responsible for the collecting of [de-spawned, spawned, updated] players so if multiple worker threads got different movement packets for same player and each generated clusterUpdateTask how did you handled that concurrency problems?

  • on the clusterUpdateTaskFinalizedCallback? but that still suffers from concurrency problems

-Do you processed the MovementPackets through the players LFE? If so, does that suffice?

Sorry for the misspelling and bad writing.
Please help me out.

My Email Address: [email protected]
My Skype:balan.narcis1

Thank you very much.

Have a great day,
Narcis

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant