Lock in FMS code

Question

Hi,
       Does anybody has idea about locking system in FMS server side code. Like we have locking system in Coldfusion and other technologies (CF lock).
Like shared objects we have lock, but what If I want to implement lock on the particular script. For example at onConnect of any user to FMS,  I have script which is doing 8-9 different tasks before or after accept the user for that FMS application session (including remoting calls).
Now if 20 users came at the same time in the same room, how will FMS execute them and process the 8-9 task, which user will be executed first and who would be next.
In short, how FMS will execute the piece of code or process for multiple user at the same time.
So locking system can fix this problem I think.
Is  there anything else we can do to make this system better.
Looking forward any help in this area. If there is any expert please suggest the best solution.
Thanks,
Amitabh Arya

Answer 1

Hi,
            Thanks for replying. Both methods are really good. First I thought to reply you as this is the best answers but then I decided to discuss it little more in depth and to reach the best solution. As you are sounding a good FMS professional to me  .
Before discussing further let me introduce with some of my concerns:
>> I am rewriting this application for one of my client. (Some other guy wrote this earlier for them)
>> In current scenarios, the application each instance (each room) has about 50 users at the time.
>> On every connect and disconnect, there is a  remoting call to update the database, writing the logs in a text file (from FMS only) and much more logic and checks.
>> There are multiple servers and every server has the same version of application code.
In 2nd solution, (this should be the perfect solution, what Adobe should code in FMS by default ) But I have few points to discuss
>>  The main part of connection (connection business logic) is depend on client side code, while I think to keep the complete code (business logic) at server side is more secure.
>> Its a long process, while you are using it with remoting. As user will come, put him in array, wait for completion of last process, and broadcast client method. Clients will call the server methods back, start the process for next user, process the checks, initiate remoting and call the remoting methods, wait for remoting callback (result) and then accept the user finally. Its still fine for application where we have 5-6 users but I think we should not count on this solution if we are talking 50 connection at the same time. If at any point FMS skips the code or doesn't process it then it will be a break and will take time to debug it.
>> The main problem is still not fixed (How FMS manage the multiple users at the same time). As multiple users will come at the same time, how can we assure that FMS will assign different index to each user or push each user in array with different index. Because the problem is not to process the one line code or multiple code lines but to manage the multiple users at the same time, who will be first and who will be next, How FMS will decide this.
In 1st solution, sounds good to me. But
>> As FMS creates different instance for each users and provide a different client id, so create a client level function at server and process the whole business logic of accepting a client in that, make more sense to me.
But I am confused that what you mean by "cannot use global variables", what kind of global variables are you talking here, is that trace or setIntervals or something else. And is there any security issue to use the client object functions to accept the clients. Please verify .
One more things, (I might be going away from topic). Do you have any idea about secure.asc file what it does.
Once again Thanks for your replying. Looking forward to your replies again 
Amitabh Arya