X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Socket%2FFramingPolicy.hh;h=5359c2710e5496e9fa918e2748202ca48473fc90;hb=bd9f9d3fd6fbcff0112a7bf48ab9284da9576b11;hp=a873239d0fe87521cd185f79d30ad94a3eb112c7;hpb=d0006132bfcb3ab442cf66b600ed3fad36f1ac2c;p=senf.git diff --git a/Socket/FramingPolicy.hh b/Socket/FramingPolicy.hh index a873239..5359c27 100644 --- 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 +// Copyright (C) 2006 +// Fraunhofer Institute for Open Communication Systems (FOKUS) +// Competence Center NETwork research (NET), St. Augustin, GERMANY +// Stefan Bund // // 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 @@ -24,8 +24,8 @@ \brief FramingPolicy public header */ -#ifndef HH_FramingPolicy_ -#define HH_FramingPolicy_ 1 +#ifndef HH_SENF_Socket_FramingPolicy_ +#define HH_SENF_Socket_FramingPolicy_ 1 // Custom includes #include "SocketPolicy.hh" @@ -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 { // 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: