04.07.2011, 07:03
I think that to get more and higher performance in every sa-mp server, OnPlayerUpdate should be handled in way other manner. Maybe on separate thread, but basically, my intention is, for future versions, have OnPlayerUpdate separated, and basically let server continue on other thread. For example, let's consider you have a code that may work a second, to get the result. Now in normal case, it would just freeze the server, but if we separate player updates in other scripts or manner, we may allow the server to work FASTER. Another example - commands. Seriously on some servers it has been awful experience of server speed in cases of using commands.
For now, it may be possible to implant that into simple code + plugin. But in future, I'd say it should be like :
When player information updates:
Sa:Mp calls Checking scripts and then callbacks.
1.Checking scripts and callback codes work in the same time.
2.Checking scripts may call callbacks or functions.
That should give closer client side script experience.
For now, it may be possible to implant that into simple code + plugin. But in future, I'd say it should be like :
When player information updates:
Sa:Mp calls Checking scripts and then callbacks.
1.Checking scripts and callback codes work in the same time.
2.Checking scripts may call callbacks or functions.
That should give closer client side script experience.
