RE: scope and presenting realtime data (fwd)

y if the last value for a server is older than n seconds (saves some io) > > else sounds good > > hth > Alexander > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 26. Mai 2004 19:39 > To: Struts Users Mailing List >

RE: scope and presenting realtime data (fwd)

hat daemon thread 3) poll only if the last value for a server is older than n seconds (saves some io) else sounds good hth Alexander -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 26. Mai 2004 19:39 To: Struts Users Mailing List Subject: Re: scope and

Re: scope and presenting realtime data (fwd)

Dear All, Thanks for all your feedback. Based on the discussion i derive following conclusions. please comment on their accuracy. 1. A Data Storage object (Say a HaspMap with the server name as a key and the N value data object as value are stored along with the last updated time)

Re: scope and presenting realtime data (fwd)

My advice may sound out of the context, but how bout actually storing each last N value to a database. this way you can even have an archive of the Last N value. Or if you dont want to setup a database, just write the last N value to a property file or text file. Regards, Irfandhy Franciscus [E

RE: scope and presenting realtime data (fwd)

- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 26. Mai 2004 14:35 To: Struts Users Mailing List Subject: RE: scope and presenting realtime data (fwd) Hi, Thanks for your response... as you rightly pointed out the data is 'near realtime' not exactly REAL-TIME.

RE: scope and presenting realtime data (fwd)

Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 26 May 2004 20:35 To: Struts Users Mailing List Subject: RE: scope and presenting realtime data (fwd) Hi, Thanks for your response... as you rightly pointed out the data is 'near realtime' not exactly REAL-

RE: scope and presenting realtime data (fwd)

Hi, Thanks for your response... as you rightly pointed out the data is 'near realtime' not exactly REAL-TIME. Yes.. we need to store in the servlet context.. but what needs to be the scope.. if scope is request, than we can show only the current value. if the scope is session, than this bean

RE: scope and presenting realtime data (fwd)

Why not store the info in the servlet context, using different keys for each server? That way if several users are all monitoring the same server they will be looking at the same set of data. Since the data is being multithreaded you will need to make sure you synchronize in the appropriate place