1 files changed, 0 insertions, 67 deletions
diff --git a/TAO/orbsvcs/orbsvcs/ESF/ESF_RefCount_Guard.h b/TAO/orbsvcs/orbsvcs/ESF/ESF_RefCount_Guard.h
deleted file mode 100644
index 84569c79bb6..00000000000
--- a/TAO/orbsvcs/orbsvcs/ESF/ESF_RefCount_Guard.h
+++ /dev/null
@@ -1,67 +0,0 @@
-// -*- C++ -*-
-
-/**
- *  @file   ESF_RefCount_Guard.h
- *
- *  $Id$
- *
- *  @author Carlos O'Ryan (coryan@cs.wustl.edu)
- *
- *  http://doc.ece.uci.edu/~coryan/EC/index.html
- */
-
-#ifndef TAO_ESF_REFCOUNT_GUARD_H
-#define TAO_ESF_REFCOUNT_GUARD_H
-
-#include "ace/config-all.h"
-
-#if !defined (ACE_LACKS_PRAGMA_ONCE)
-# pragma once
-#endif /* ACE_LACKS_PRAGMA_ONCE */
-
-#include "tao/Versioned_Namespace.h"
-
-TAO_BEGIN_VERSIONED_NAMESPACE_DECL
-
-/**
- * @class TAO_ESF_RefCount_Guard
- *
- * @brief Reference count based guard.
- *
- * A common idiom used on event services is to increment a
- * reference count before starting a long running operation.
- * The system can then execute the operation without any risk of
- * having the underlying object destroyed.  The advantage of using
- * a reference count is that no mutex or lock needs to be held
- * while the operation is beign executed.
- */
-template<class T>
-class TAO_ESF_RefCount_Guard
-{
-public:
-  /// Constructor
-  TAO_ESF_RefCount_Guard (T &refcount);
-
-  /// Destructor
-  ~TAO_ESF_RefCount_Guard (void);
-
-protected:
-  /// The reference count
-  T &refcount_;
-};
-
-TAO_END_VERSIONED_NAMESPACE_DECL
-
-#if defined (__ACE_INLINE__)
-#include "orbsvcs/ESF/ESF_RefCount_Guard.i"
-#endif /* __ACE_INLINE__ */
-
-#if defined (ACE_TEMPLATES_REQUIRE_SOURCE)
-#include "orbsvcs/ESF/ESF_RefCount_Guard.cpp"
-#endif /* ACE_TEMPLATES_REQUIRE_SOURCE */
-
-#if defined (ACE_TEMPLATES_REQUIRE_PRAGMA)
-#pragma implementation ("ESF_RefCount_Guard.cpp")
-#endif /* ACE_TEMPLATES_REQUIRE_PRAGMA */
-
-#endif /* TAO_ESF_REFCOUNT_GUARD_H */