From 278b2bdd211ecefb9d92f9b9dfdcc39d5564fd98 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Tue, 8 Feb 2005 14:04:57 +0000 Subject: [PATCH] Admit explicitely that the hacker's example is really a hacker's example. --- org.glite.lb.client/doc/README-notify | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/org.glite.lb.client/doc/README-notify b/org.glite.lb.client/doc/README-notify index 481070a..c563cd1 100644 --- a/org.glite.lb.client/doc/README-notify +++ b/org.glite.lb.client/doc/README-notify @@ -20,10 +20,17 @@ For a notification delivery, a special deamon, a notification interlogger is use -Notification example --------------------- +Notification test +----------------- + +The four steps bellow describe basic testing procedure of the notification +system by creating a fake job record in the LB server, registering +a notification on any state change of this job, and forcing the job state +change. -In the next steps, you will be instucted how to register for a notification and how to triger this registration on the LB server in order to receive registration. Our example program 'glite-lb-notify' is used as a notification client here. It uses mentioned client API calls to manipulate with registrations. +Our example program 'glite-lb-notify' is used as a notification +client here. It uses mentioned client API calls to manipulate with +registrations. 1) Register a job -- 1.8.2.3