From f493dc0b9c43dab254d9d9b6647cb6df98361c88 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ale=C5=A1=20K=C5=99enek?= Date: Wed, 24 Feb 2010 15:20:00 +0000 Subject: [PATCH] more verbose description of job registration (thorough fix for #31592) --- org.glite.lb.doc/src/LBUG-Introduction.tex | 7 +++++++ org.glite.lb.doc/src/components.tex | 1 + 2 files changed, 8 insertions(+) diff --git a/org.glite.lb.doc/src/LBUG-Introduction.tex b/org.glite.lb.doc/src/LBUG-Introduction.tex index fb6a3fd..ed38e3c 100644 --- a/org.glite.lb.doc/src/LBUG-Introduction.tex +++ b/org.glite.lb.doc/src/LBUG-Introduction.tex @@ -629,6 +629,13 @@ the same job may be refused with a ``no such job'' error report. Therefore submission of a job to the WMS is the only synchronous event logging that does not return until the job is successfully registered with the \LB server. +Moreover, the initial registration is sent by the \LB client library in +parallel to \LB proxy (Sect.~\ref{s:proxy}) and \LB server. + +On the other hand, even the registration event may carry large data +(e.g. JDL of huge job collection). Therefore +also an additional asychronous variant is used, causing two job registration +events appear typically. % explicitní -- user tagy, ACL However, the user may also store information into the \LB explicitly diff --git a/org.glite.lb.doc/src/components.tex b/org.glite.lb.doc/src/components.tex index 3f6fa07..cbb60cf 100644 --- a/org.glite.lb.doc/src/components.tex +++ b/org.glite.lb.doc/src/components.tex @@ -122,6 +122,7 @@ pending events belonging to this handle accordingly. % asi nepotrebujeme \subsubsection{Clients} \subsubsection{Proxy} +\label{s:proxy} \emph{\LB proxy} is the implementation of the concept of local view on job state (see \ifx\insideUG\undefined{\cite{lbug}}\else{Sect.~\ref{local}}\fi). Since -- 1.8.2.3