How are processed DWR requests handled differently, not shipped on the server side?

I wrote a DWR client in Python that I use to automate tests running on the DWR website. Until now, all the calls that I make are single, unpaired requests, and I make several requests, all in single-threaded mode.

I noticed that when I use the browser, some calls carry over to one request. Besides the bundle, are there any differences from how the calls are handled by the server? I believe that they are parsed and processed sequentially, and from what I tested there are no noticeable differences. However, I am concerned that there may be some hidden traps, and I need my python client to simulate browser usage.

+5
source share
1 answer

In almost all cases, batch processing acts the same as a collection of synchronous unrelated calls. See DWR Batching Cautions for Potential Traps.

0
source