<?xml version="1.0"?>
<rss version="2.0">
<channel>
<title>StresStimulus Forum - SUPPORT QUESTIONS - Async Calls - Messages</title>
<link>https://www.stresstimulus.com/forum/async-calls-662</link>
<description>StresStimulus Forum - SUPPORT QUESTIONS - Async Calls - Messages</description>
<language>en-us</language>
<docs>http://blogs.law.harvard.edu/tech/rss</docs>
<generator>Jitbit AspNetForum</generator>
<pubDate>Thu, 11 Oct 2018 22:06:02 GMT</pubDate>
<lastBuildDate>Thu, 11 Oct 2018 22:06:02 GMT</lastBuildDate>
<item>
<link>https://www.stresstimulus.com/forum/async-calls-662</link>
<title>Message from George @StresStimulus</title>
<description><![CDATA[While StresStimulus does not emulate full browser’s DOM behavior, it by default attempts to realistically simulate concurrency of async (AJAX) calls (requests) according to the application logic by using various information such as recorded sequence and requests’ content-type. Some of the request concurrency rules are described here <a href="http://support.stresstimulus.com/display/doc49/Request+concurrency" target="_blank" rel="nofollow">http://support.stresstimulus.com/display/doc49/Request+concurrency</a><br/><br/><br/>   <br/>  Additionally,  you can override the default behavior by setting concurrency mode for individual requests, as described here  <a href="http://support.stresstimulus.com/display/doc49/Request+Properties" target="_blank" rel="nofollow">http://support.stresstimulus.com/display/doc49/Request+Properties</a>  in the Concurrency mode section.]]></description>
<pubDate>Thu, 11 Oct 2018 22:06:02 GMT</pubDate>
</item>
<item>
<link>https://www.stresstimulus.com/forum/async-calls-662</link>
<title>Message from Unregistered User</title>
<description><![CDATA[How does ST handle async calls. Are all the requests executed sequentially or the tool will handle the calls as per Application logic - sequential or parallel.]]></description>
<pubDate>Thu, 11 Oct 2018 09:03:54 GMT</pubDate>
</item>
</channel>
</rss>
