X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Socket%2FSocketPolicy.hh;h=708f18a3125fb7eabe23b48e228139efc6d6b335;hb=3cde315703150449c967936e3f064fa5928a1cc2;hp=c7ed63ab6b614b59cb1741dd1fe09416a47cfad7;hpb=15c5e1939d77dfea97da38df7526bcb84a53460b;p=senf.git

diff --git a/Socket/SocketPolicy.hh b/Socket/SocketPolicy.hh
index c7ed63a..708f18a 100644
--- a/Socket/SocketPolicy.hh
+++ b/Socket/SocketPolicy.hh
@@ -24,12 +24,20 @@
     \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