If you want asynchronous processing on the backend for your requests I'd recommend taking a look at the JMS adapter. Rather than making a RemoteObject call you'd send your requests to the server using a Producer and listen for async results using a Consumer. You'd want to use an inbound request topic for your clients to send their requests to, and you can write a Java JMS client that handles messages sent to this topic asynchronously via a worker pool or something similar. Reponses can be sent to a second outgoing response topic that the clients have subscribed to. You can use message headers and Consumer selector expressions to target responses back to the proper client.
HTH, Seth ________________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of jbergamotto Sent: Friday, November 17, 2006 4:17 AM To: [email protected] Subject: [flexcoders] FDS not receiving calls asynchronously I am having an issue with concurrency using FDS. I have six calls going to the same destination (all different methods) at the same time. Setting up logging on the client side I see that Flex is sending the calls all at the same time, however in the server log (being recorded at the beginning and end of each method) I notice that each call is being completed before the next call is started. There is no code to block that I am writing, in fact the first line of the method writes to a log. Inside the method there is some message retrieval happening and each of the calls can take a different amount of time, the calls were broken up to allow for retrieval to come back asap, however the synchronous behaviour is preventing us from having 2 longer calls running at the same time. Are there settings that I am unaware of in the remoting-config that can fix this behaviour? Is there code in the messagebromer that is making this synchronous? I have tried increasing the framerate of the main application mxml and utilizing the callLater feature, but there is no change in behaviour.
