NEW FILE HEADER / COPYRIGHT FORMAT

[senf.git] / Socket / FramingPolicy.hh

diff --git a/Socket/FramingPolicy.hh b/Socket/FramingPolicy.hh
index a873239..dece080 100644 (file)
--- a/Socket/FramingPolicy.hh
+++ b/Socket/FramingPolicy.hh
@@ -1,9 +1,9 @@
 // $Id$
 //
-// Copyright (C) 2006 
-// Fraunhofer Institut fuer offene Kommunikationssysteme (FOKUS)
-// Kompetenzzentrum fuer Satelitenkommunikation (SatCom)
-//     Stefan Bund <stefan.bund@fokus.fraunhofer.de>
+// Copyright (C) 2006
+// Fraunhofer Institute for Open Communication Systems (FOKUS) 
+// Competence Center NETwork research (NET), St. Augustin, GERMANY 
+//     Stefan Bund <g0dil@berlios.de>
 //
 // This program is free software; you can redistribute it and/or modify
 // it under the terms of the GNU General Public License as published by
@@ -39,23 +39,23 @@ namespace senf {
     /// @{
 
     /** \brief FramingPolicy for stream oriented sockets
-       
-       This policy does not explicitly modify the SocketHAndle
-       API. It however affects the semantics of the read and write
-       operations. On a stream oriented socket, read() and write()
-       operations may be combined, the boundary between separate
-       write() calls will be lost on the receiving side.
+
+        This policy does not explicitly modify the SocketHAndle
+        API. It however affects the semantics of the read and write
+        operations. On a stream oriented socket, read() and write()
+        operations may be combined, the boundary between separate
+        write() calls will be lost on the receiving side.
      */
     struct StreamFramingPolicy : public FramingPolicyBase
     {};
 
     /** \brief FramingPolicy for datagram oriented sockets
 
-       This policy does not explicitly modify the SocketHAndle
-       API. It however affects the semantics of the read and write
-       operations. On a datagram socket, each read() or write() call
-       we read or write a single datagram. Datagram boundaries are
-       kept intact accross the network.
+        This policy does not explicitly modify the SocketHAndle
+        API. It however affects the semantics of the read and write
+        operations. On a datagram socket, each read() or write() call
+        we read or write a single datagram. Datagram boundaries are
+        kept intact accross the network.
      */
     struct DatagramFramingPolicy : public FramingPolicyBase
     {};
@@ -73,5 +73,10 @@ namespace senf {
 \f
 // Local Variables:
 // mode: c++
+// fill-column: 100
 // c-file-style: "senf"
+// indent-tabs-mode: nil
+// ispell-local-dictionary: "american"
+// compile-command: "scons -u test"
+// comment-column: 40
 // End: