It really depends on your application. I've some applications that poll important lists, but if those lists get long, we'll need to put some more thought into the way it works.
If it's a short list that's likely to change a lot, poll the whole thing. If it's a long list, and there's unlikely to be many changes, you'll need something more complicated like polling a "last updated" time, or "fetch me the changes since X" sort of method, or even an XML socket so your server can push change events through to the Flex app. And that's just a few of no doubt many different ways to approach the issue. -Josh On Tue, Jul 8, 2008 at 3:01 PM, Alan <[EMAIL PROTECTED]> wrote: > I'm building a large Flex app for the first time and I'm curious about > how often I should be sending queries to the remote database? Does any > one have some advice or general guidelines when to determine if > requesting small amounts out data based on user triggered events, or > to load a larger amount of data that is then manipulated locally? > > > Alan > > > > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
