Open
Description
When I implemented simulatedLatencyMs using setTimeout, I assumed that multiple calls to setTimeout with the same interval would have the callbacks executed in the same order that the timeouts were created.
After having some message-ordering issues with react-native that went away when I disabled simulatedLatencyMs, I think it's not safe to rely on. Some quick googling indicates I shouldn't rely on it: http://stackoverflow.com/q/11771558/515380
It might make sense just to remove this functionality and let developers use their own tools to simulate latency when developing locally. Unfortunately, chrome dev tools doesn't support websocket yet for throttling.