On Fri, Oct 14, 2005 at 11:59:27AM +0100, Burke, S (Stephen) wrote:
>
> Separately there is the CESEBind (close SE) information, which is
> published by a CE, and which has traditionally carried not only the CESE
> binding but also information for classic SEs on where to store the data,
> hence all classic SEs need to be bound to a CE.
Hello,
I am bit confused. Since Classic SEs publish information like this:
GlueSAPath: /storage/atlas
then why is the CESEBind information still needed in order to find where
to store the data? Is there a technical reason for this or is it just
something left from the past?
Cheers,
--
Kyriakos Ginis, PhD Candidate
Software Engineering Laboratory
National Technical University of Athens
|