Forum Discussion
punekar
13 years agoOccasional Contributor
Sergei -
Thanks for taking time to respond.
You will have to change your mind sooner or later about exposing the scenario/script format to users. Mercury/HP tried to keep this under wraps for the longest time and didn't succeed. People reverse engineered it and figured out the mechanics. Today everyone knows about the LCC precompiler and their custom object format. It helped for a more "aware" user base who would comprehend runtime issues with controller/generator communication etc.
Key takeaway - Information, and openness, is better than a black box philosophy.
Also, the results format today has to absolutely change. You have to populate it into either CSV or database. There is really no reason why users should not be in control of their own data. All you have to do is output raw numbers to CSV to make it immediately useful. We can then import it into spreadsheets and do our own reporting from there onwards.
Please tell me there is a plan to ensure this is happening in a future release.
About support for other protocols - why not include support for a compiled virtual user? Let us write our code in Visual C++, compile to object format, and have LoadComplete simply invoke that compiled code at runtime.
Thanks for taking time to respond.
You will have to change your mind sooner or later about exposing the scenario/script format to users. Mercury/HP tried to keep this under wraps for the longest time and didn't succeed. People reverse engineered it and figured out the mechanics. Today everyone knows about the LCC precompiler and their custom object format. It helped for a more "aware" user base who would comprehend runtime issues with controller/generator communication etc.
Key takeaway - Information, and openness, is better than a black box philosophy.
Also, the results format today has to absolutely change. You have to populate it into either CSV or database. There is really no reason why users should not be in control of their own data. All you have to do is output raw numbers to CSV to make it immediately useful. We can then import it into spreadsheets and do our own reporting from there onwards.
Please tell me there is a plan to ensure this is happening in a future release.
About support for other protocols - why not include support for a compiled virtual user? Let us write our code in Visual C++, compile to object format, and have LoadComplete simply invoke that compiled code at runtime.