| || |
Winsock correlation-Unique value in \'send\' buffer
Have recorded a script (for a client-server) using the Winsock protocol (yes, the application is not recognizing any other protocol including, ODBC). Since, this uses 'Gryphon' over TCP/IP. Now, when I view the 'data.ws' part, the unique value to be correlated is present <u>only</u> in the 'send' buffer. I have re-recorded the script and compared the 1st & 2nd. Both, scripts have the unique values in the send part. Vugen allows me only to create a parameter only for data in the 'receive' buffer not otherwise. Now, have I missed anything? This is the only transaction of this nature. The other 10 transactions have been correlated and running fine.
Any leads is much appreciated. (I'm getting back to the basics to see if I missed out anything before someone here asks me to, [img]/images/graemlins/wink.gif[/img] thought I'll consult here in parallel.) Thanks.
P.S. Does this post need the usual queries to be answered? If so, please let me know. Thanks.
Re: Winsock correlation-Unique value in \'send\' buffer
You may need to speak with the developer for information on the algorithm to produce the value in question. You have three sources of data going to the server
<ul type="square">[*]Parameterized Data[*]Correlated data (Session, State, Time, Businesss)[*]<font color="red">Output of client side algorithms</font>[/list]
As you have exhausted the first two options, then you are left with the last option (in <font color="red">red</font> above).
Replace ineffective offshore contracts, LoadRunnerByTheHour
. Starting @ $19.95/hr USD.
Put us to the test, skilled expertise is less expensive than you might imagine.
Twitter: @LoadRunnerBTH @PerfBytes