X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Socket%2FSocketPolicy.hh;h=708f18a3125fb7eabe23b48e228139efc6d6b335;hb=3601c83f32cad85638739f891218f1e5d9fa0896;hp=297a469aafc156e691f2ac5ea069d0696797b901;hpb=494e197e719a49fba726d90f668c2d96c02c744b;p=senf.git
diff --git a/Socket/SocketPolicy.hh b/Socket/SocketPolicy.hh
index 297a469..708f18a 100644
--- a/Socket/SocketPolicy.hh
+++ b/Socket/SocketPolicy.hh
@@ -21,15 +21,23 @@
// 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
/** \file
- \brief SocketPolicy public header
+ \brief Policy Framework public header
\todo We should probably remove BufferingPolicy from the
- interface, it does not make much sense (how did I come to include
- it ??)
+ interface, it does not make much sense (how did I come to
+ include it ??)
\todo Do we want to support separate read and write policies. This
- allows to treat pipes within this framework however, is this worth
- the effort?
+ allows to treat pipes within this framework however, is this
+ worth the effort?
+
+ \idea Creating a new Socket will create three new instances (The
+ handle, the body and the policy) of which two (body and
+ policy) live on the heap. This is expensive. We should check,
+ wether we can make all the policy classes to singletons and
+ assign the same instance to all socket bodies with the same
+ policy. This would reduce the number of allocations per socket
+ handle to one.
*/
/** \defgroup policy_group The Policy Framework
@@ -206,8 +214,7 @@
senf::ConnectedCommunicationPolicyIs is based on the \c
boost::enable_if template).
- \see \ref policy_framework \n
- \ref extend_policy \n
+ \see \ref extend_policy \n
The Boost enable_if utility \n
The Boost.MPL library \n
The Boost.Preprocessor library