Do not dismiss Paul's advice... 300 hundrend or even 2000 clients is not a problem...Polling every second would not create a problem on a server with correct caches and so on...
Add your app in facebook and then you have a problem (possibly 1-4 millions registers in first couple of months) On Thu, Oct 23, 2008 at 2:14 AM, Josh McDonald <[EMAIL PROTECTED]> wrote: > I'd start the timer only when a successful result returns, and then I'd > set it for (pollingFrequencyDelay + Math.round(Math.random() * > lastResponseTime)) each time, so as to slow things down a little when it's > under load. > > -Josh > > > On Thu, Oct 23, 2008 at 8:50 AM, Paul Andrews <[EMAIL PROTECTED]> wrote: > >> Just one more word of caution. The timer MUST allow enough time for the >> server to complete the request that you have asked of it. The last thing >> that you want is to stack up requests to the server. Ideally in this timer >> environment you won't make a request to the server while the last request >> hasn't yet completed. >> >> Bit harder than at first sight, isn't it? >> >> Paul >> >> ----- Original Message ----- >> *From:* Paul Andrews <[EMAIL PROTECTED]> >> *To:* [email protected] >> *Sent:* Wednesday, October 22, 2008 11:39 PM >> *Subject:* Re: [flexcoders] Re: How to keep Tree control synchronized >> with the database. Please Help >> >> A word of caution Anuj. >> >> I don't know if your timer works once a second or once a minute, or once >> every two minutes. If you have only one online user, it's not too huge a >> deal either way. If you have a hundred users you can cause big problems for >> your server. The timer technique just makes the best of a bad job. Usually a >> lot of care is taken over database and query design to minimise the impact >> of large numbers of users. Unfortunately the timer technique gives the >> server a lot of work even when the number of users is quite small. >> >> Remember a timer on the client just affects one user and there's usually >> processor power to spare. A timer in conjunction with a server database >> access stresses the server. It stresses the server a lot. >> >> End of cautionary note. >> >> Paul >> >> ----- Original Message ----- >> *From:* anuj sharma <[EMAIL PROTECTED]> >> *To:* [email protected] >> *Sent:* Wednesday, October 22, 2008 11:31 PM >> *Subject:* Re: [flexcoders] Re: How to keep Tree control synchronized >> with the database. Please Help >> >> Bingo Guys >> Thats' exactly what i need. Tracy's Timer example works perfect for me. >> Again thanks a lot for your help. >> Anuj >> >> On Wed, Oct 22, 2008 at 2:29 PM, john fisher <[EMAIL PROTECTED]> wrote: >> >>> Anuj >>> >>> I meant, "search through the online adobe docs for 'timer polling >>> example' or other keywords like those." >>> >>> there are many many examples in the online docs at Adobe. >>> >>> John >>> >>> >>> anuj sharma wrote: >>> > Hi John >>> > I am not sure i get what you are trying to say. Can you be please >>> elaborate >>> > little bit more. >>> > Thanks >>> > Anuj >>> > >>> > On Wed, Oct 22, 2008 at 10:13 AM, john fisher <[EMAIL >>> > PROTECTED]<john%40jpfisher.net>> >>> wrote: >>> > >>> > >>> >> @mark: thanks will check it out >>> >> @anuj: >>> >> this is just exactly what the adobe sample code does, except not >>> >> directly to the database. >>> >> >>> >> anuj sharma wrote: >>> >> >>> >>> ... Can I use the Timer class to create a timer instance >>> >>> >>> >>> which will periodically call HTTP a >>> >>> >>> >> >>> >> >>> >> >>> > >>> > >>> >> >> > > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > Like the cut of my jib? Check out my Flex blog! > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] > :: http://flex.joshmcdonald.info/ > > -- Fotis Chatzinikos, Ph.D. Founder, Phinnovation [EMAIL PROTECTED],
