I wonder if anybody experienced something like that.
It's quite a big project, currently running with Flex SDK 3.5.
After converting to SDK 4.1 and making all required adjustment the UI runs as good as before, with one problem - creation of new complex UI components takes much longer (3-5 times). Creation of some components involves a number of server calls, which according to Network Monitor do run much longer (e.g. 13 seconds instead of 4).
I'm considering 2 possibilities:
1. Something in UI is holding all threads, preventing service calls from finishing promptly, and making impression of slow network.
2. Server communication somehow got much slower. Against that the fact is because server calls are asynchronous they shouldn't prevent UI from drawing at least empty components.
Server code is the same for old and new UI, it runs Spring, Hibernate, Jetty (in dev mock) or Tomcat (on dev server), LCDS 3.1.
I've tried several LCDS 3.1 libraries with and without patches, SDK3 and SDK4 specific, with the same result.
Flash Player 10.1.xx debug.
Can you mock up the server calls with local data and remove the network requests from the equation? Also, are the number of network calls made the same when using 3.5 and 4.1?
It turned out that delays where caused by slow instantiation of visual components.
Presumably Network Monitor registers facts that server communication is initiated (queued?), but doesn't say when Flash Player frees resources to make actual calls (switch to the second Frame?). Or something like that.