Hi,
I have built a virtual world using your platform.
http://www.ekoloko.com
We have around 200,000 registered users and over 2000 concurrent users at peak time.
First I'd like to thank you for your implementation and support.
I use user variables to keep the live data of the users.
Some vars like user position are changed at the client side and others by the server.
I want to limit the variables change by users only to the ones I allow to change and block others form client change.
I could not find an API allowing me to handle user variable change at server side before broadcast.
Of course I handle the server side using JAVA extension.
Your help is appreciated.
Handle UserVaraiable change at server side
Hi,
Your client should call your server side extension requiring the variables update and passing any data that your custom code will validate before completing the process, refusing the clients that don't have permissions.
You should perform the User Variable updates from server side.I want to limit the variables change by users only to the ones I allow to change and block others form client change.
Your client should call your server side extension requiring the variables update and passing any data that your custom code will validate before completing the process, refusing the clients that don't have permissions.
Thanks for the reply.
It is true that I can always Zone Extension as i do in many cases.
However this solution is a bit problematic since my Extension Handler threads are very busy.
Loading them with more load (user position is quiet a load) while the system handler threads are idle is a pitty.
Is there a hook where I can handle cilent user vars change?
Many thanks.
It is true that I can always Zone Extension as i do in many cases.
However this solution is a bit problematic since my Extension Handler threads are very busy.
Loading them with more load (user position is quiet a load) while the system handler threads are idle is a pitty.
Is there a hook where I can handle cilent user vars change?
Many thanks.
You can always add more if it's a matter of parallel processing. If not it won't help.However this solution is a bit problematic since my Extension Handler threads are very busy.
What I mean is that if your server side code performs long running operations (like http calls, db queries etc...) it is recommendable to add more threads for better scalability.
On the contrary if your code performs heavy computation adding more threads won't any good.
In that case you can try optimizing the code or move to a more powerful hardware.