5 May
2012
5 May
'12
11:58 a.m.
On 5/5/12 1:47 , Fred Baker wrote:
Well, a suggestion.
Suppose that every time a probe does its test, it also reads<something> from RIPE that tells it the address of the target to probe next. This would allow RIPE (passing along your instructions, or executing its own) that could implement any of a variety of scenarios, and change them from time to time.
That is already there. Probes are under full control of the Atlas infrastructure. The problem is more that the Atlas backend is very complex distributed system. So it takes time before the necessary datastructures and database tables are in place to really express the concept of looping over all probe.