LogService
libdadi: utility tools for distributed applications
 All Classes Functions Variables
ComponentList.hh
1 /****************************************************************************/
2 /* defines a list that holds all information on componentes connected to */
3 /* the new Logservice */
4 /* */
5 /* Author(s): */
6 /* - Georg Hoesch (hoesch@in.tum.de) */
7 /* - Cyrille Pontvieux (cyrille.pontvieux@edu.univ-fcomte.fr) */
8 /* */
9 /* This file is part of DIET . */
10 /* */
11 /* Copyright (C) 2000-2003 ENS Lyon, LIFC, INSA, INRIA and SysFera (2000) */
12 /* */
13 /* - Frederic.Desprez@ens-lyon.fr (Project Manager) */
14 /* - Eddy.Caron@ens-lyon.fr (Technical Manager) */
15 /* - Tech@sysfera.com (Maintainer and Technical Support) */
16 /* */
17 /* This software is a computer program whose purpose is to provide an */
18 /* distributed logging services. */
19 /* */
20 /* */
21 /* This software is governed by the CeCILL license under French law and */
22 /* abiding by the rules of distribution of free software. You can use, */
23 /* modify and/ or redistribute the software under the terms of the CeCILL */
24 /* license as circulated by CEA, CNRS and INRIA at the following URL */
25 /* "http://www.cecill.info". */
26 /* */
27 /* As a counterpart to the access to the source code and rights to copy, */
28 /* modify and redistribute granted by the license, users are provided */
29 /* only with a limited warranty and the software's author, the holder */
30 /* of the economic rights, and the successive licensors have only */
31 /* limited liability. */
32 /* */
33 /* In this respect, the user's attention is drawn to the risks */
34 /* associated with loading, using, modifying and/or developing or */
35 /* reproducing the software by the user in light of its specific status */
36 /* of free software, that may mean that it is complicated to */
37 /* manipulate, and that also therefore means that it is reserved for */
38 /* developers and experienced professionals having in-depth computer */
39 /* knowledge. Users are therefore encouraged to load and test the */
40 /* software's suitability as regards their requirements in conditions */
41 /* enabling the security of their systems and/or data to be ensured and, */
42 /* more generally, to use and operate it in the same conditions as */
43 /* regards security. */
44 /* */
45 /* The fact that you are presently reading this means that you have had */
46 /* knowledge of the CeCILL license and that you accept its terms. */
47 /* */
48 /****************************************************************************/
49 /* $Id$
50  * $Log$
51  * Revision 1.3 2007/09/03 06:33:24 bdepardo
52  * Removed IOR, it was useless.
53  *
54  * Revision 1.2 2007/08/31 16:41:17 bdepardo
55  * When trying to add a new component, we check if the name of the component exists and if the component is reachable
56  * - it the name already exists:
57  * - if the component is reachable, then we do not connect the new component
58  * - else we consider that the component is lost, and we delete the old component ant add the new one
59  * - else add the component
60  *
61  * Revision 1.1 2004/01/09 11:07:12 ghoesch
62  * Restructured the whole LogService source tree.
63  * Added autotools make process. Cleaned up code.
64  * Removed some testers. Ready to release.
65  *
66  ****************************************************************************/
67 
68 #ifndef _COMPONENTLIST_HH_
69 #define _COMPONENTLIST_HH_
70 
71 #include "FullLinkedList.hh"
72 #include "LogComponent.hh"
73 
78 struct ComponentElement {
79  ComponentConfigurator_var componentConfigurator;
80  CORBA::String_var componentName;
81 };
82 
89 typedef FullLinkedList<ComponentElement> ComponentList;
90 
91 // Eventually define a function that takes an iterator
92 // and a componentName as input and sets the iterators
93 // currentElement to the component with the given name ?
94 
95 #endif
Generated on Mon Aug 19 2013 21:50:34 for LogService by   doxygen 1.8.4