It's interesting that you found that. The original response was written to the VSTS forum user who was asking for something that the VSTS approach does not allow, and which eValid does.
As you can see, even though our response was criticized for being inappropriate the Microsoft guy did respond and the conversation went around a couple of times back and forth.
There was no intention to be negative about the all-HTTP protocol recording -- after all, eValid has the ability to extract the HTTP sequence and play it back in the eVlite part of the LoadTest engine -- but the original post was from a user who needed to record at a "more internal to the browser" mode.
Looking back on this conversation, to be honest, the thinking here is that we could have been more careful with the language, but even so, we stand by it as it stands.
Happy to answer further questions about this. Let us know!
* eValid Architecture Team
