I'm writing an application that control connections from portables clients, receiving and sending some informations from an Oracle database. I'm using mutex to control the use of connections context. I'm using a structure program like in SampleSocketPort demo.
In this part, I think it's ok, but I want to know if two clients send some information at the same time, how Pending is called? The client must wait until the other be finished? Or the Pending is called as thread, and the responde would be almost the same time? It's hard to the client wait the reponse from a queue, because if I have large number of clients I'll be dead?
If the Pending is called like in a queue, it isn't better to change the structure of my program to something like in tcpsession demo?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
I'm writing an application that control connections from portables clients, receiving and sending some informations from an Oracle database. I'm using mutex to control the use of connections context. I'm using a structure program like in SampleSocketPort demo.
In this part, I think it's ok, but I want to know if two clients send some information at the same time, how Pending is called? The client must wait until the other be finished? Or the Pending is called as thread, and the responde would be almost the same time? It's hard to the client wait the reponse from a queue, because if I have large number of clients I'll be dead?
If the Pending is called like in a queue, it isn't better to change the structure of my program to something like in tcpsession demo?
Thanks