Forum Discussion
AlexKaras
15 years agoChampion Level 3
Hi Roman,
I may be wrong, or it may be specific to your application, but according to my understanding, (in http) the server does not try to push anything out until it receives the request from the client. (Otherwise, it looks like the server keeps some list of the clients and constantly in cycle tries to 'ping' these clients and send them something if they reply. Such approach seems to be very resource wasteful and may be treated by the (anti-virus/firewall) software as an attack attempt.)
The request from the client may be explicit (triggered by the button press) or implicit (executed on the client start). This is completely irrelevant from the load-testing functionality point of view, as the functionality cares only about requests/responces sequence.
So I think that TestComplete load-testing functionality should work for you after you've found how to handle session ids.
I may be wrong, or it may be specific to your application, but according to my understanding, (in http) the server does not try to push anything out until it receives the request from the client. (Otherwise, it looks like the server keeps some list of the clients and constantly in cycle tries to 'ping' these clients and send them something if they reply. Such approach seems to be very resource wasteful and may be treated by the (anti-virus/firewall) software as an attack attempt.)
The request from the client may be explicit (triggered by the button press) or implicit (executed on the client start). This is completely irrelevant from the load-testing functionality point of view, as the functionality cares only about requests/responces sequence.
So I think that TestComplete load-testing functionality should work for you after you've found how to handle session ids.
Related Content
- 11 months ago
Recent Discussions
- 7 hours ago