The problem you may run into is processing the response from your remote request. If the response is large or has complex data types, the native parsers/deserializers can be very slow. While the response is being processed you might have a freeze, sometimes a very significant one.
There are a lot of things you can do to work around it... get data in smaller chunks, write your own custom responders, or we have had some success using workers to process the results before returning the processed response to the main SWF. What you choose to do depends on your backend infrastructure and what communications/API frameworks you are using. In my experience, with less complex/smaller data sets I've had good luck avoiding workers and simply suppressing attempts to convert objects back to strong types and instead writing my own deserializers. Jesse On Nov 21, 2013, at 6:22 AM, Mark Line <[email protected]> wrote: > Yes that is correct. > > Like a normal Flex event, you just set up listeners functions. The app > won't just stop executing while waiting for the resultEvent or faultEvent. > > It's up to you to manage the flow and control though > > -----Original Message----- > From: Mark Fuqua [mailto:[email protected]] > Sent: 21 November 2013 14:12 > To: [email protected] > Subject: RemoteObject question > > I have to do syncing between SQLite and remote database. In my research, > there are mentions that asynchronous RemoteObject requests will not freeze > the UI. Is that true? FWIW, this is a mobile application. > > > > If this is true, it simplifies the process a bit. > > > > Actionscript workers seem a bit complicated for a NOOB and don't work for > IOS. If RemoteObjects won't freeze my UI, I can stop worrying about > multi-threading or pseudo multi-threading, which I guess is actually what > Workers are. > > > > Mark Fuqua > > > > [email protected] > > > > 2301 Mount Carmel Road > > Parkton, MD 21120 > > (410) 215-7356 > > > > www.availdata.com > > > >
