Project

General

Profile

Bug #3124

Automatically refresh ecogrid sources (endpoints) once per Kepler

Added by ben leinfelder over 11 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Category:
data access
Target version:
Start date:
02/01/2008
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3124

Description

Now that there are two ways in which to refresh the available Ecogrid services (as registered in the registry), the refresh should only happen once per Kepler window.
Currently the autorefresh will happen once for each Kepler window when the user selects the Data tab.
Since there has been a lot of time devoted to making startup quick, the refresh should not slow down the start up of Kepler.
And, of course, the user can always manually refresh the sources with the "Refresh" button that is found on the sources tab.


Related issues

Blocks Kepler - Bug #2490: Get ecogrid endpoints from Ecogrid registryResolved07/17/2006

History

#1 Updated by ben leinfelder over 11 years ago

from 1.0.0 release meeting:
-at startup, queue a thread for refreshing the endpoints after a small delay (~minute)

#2 Updated by ben leinfelder over 11 years ago

data sources are now refreshed by a new thread that is scheduled to execute 30 seconds (configurable in config.xml) after kepler start up.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 3124

Also available in: Atom PDF