X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Socket%2FFramingPolicy.hh;h=5359c2710e5496e9fa918e2748202ca48473fc90;hb=532240d72e09e19e57fac9bb55c2560b9c9e5b97;hp=96a4b98a3abe45a54ccdef283bb3f7c6d6080ff9;hpb=c52cd7d87dbb525c1267aad27391b8b7365dbb57;p=senf.git diff --git a/Socket/FramingPolicy.hh b/Socket/FramingPolicy.hh index 96a4b98..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 @@ -20,8 +20,12 @@ // Free Software Foundation, Inc., // 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -#ifndef HH_FramingPolicy_ -#define HH_FramingPolicy_ 1 +/** \file + \brief FramingPolicy public header + */ + +#ifndef HH_SENF_Socket_FramingPolicy_ +#define HH_SENF_Socket_FramingPolicy_ 1 // Custom includes #include "SocketPolicy.hh" @@ -29,16 +33,36 @@ //#include "FramingPolicy.mpp" ///////////////////////////////hh.p//////////////////////////////////////// -namespace satcom { -namespace lib { +namespace senf { + + /// \addtogroup policy_impl_group + /// @{ + + /** \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. + */ 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. + */ struct DatagramFramingPolicy : public FramingPolicyBase {}; -}} + /// @} + +} ///////////////////////////////hh.e//////////////////////////////////////// //#include "FramingPolicy.cci" @@ -49,5 +73,10 @@ namespace lib { // Local Variables: // mode: c++ -// c-file-style: "satcom" +// fill-column: 100 +// c-file-style: "senf" +// indent-tabs-mode: nil +// ispell-local-dictionary: "american" +// compile-command: "scons -u test" +// comment-column: 40 // End: