X-Git-Url: https://git.teslayout.com/public/public/public/?a=blobdiff_plain;f=include%2Fanna%2Fdiameter%2Fcodec%2FMessage.hpp;h=376fa3948bfa833e34c589dafa68da4824e59bbf;hb=23f8d538e91355cecfc96636f16597a2a48649ac;hp=32aa932206ca29dcd84fc2a8667cb5fcafb14f2b;hpb=687b0fa0b7c8440f71837334b0b29c28dfae2dca;p=anna.git diff --git a/include/anna/diameter/codec/Message.hpp b/include/anna/diameter/codec/Message.hpp index 32aa932..376fa39 100644 --- a/include/anna/diameter/codec/Message.hpp +++ b/include/anna/diameter/codec/Message.hpp @@ -189,12 +189,9 @@ public: * may occur. If you add elements (vendors, avps, messages) is not a problem. * * IMPORTANT NOTES: - * 1) if you want to reuse the message, as a recommendation, you should set engine to - * NULL or use #clear. In that way, next operation will adjust automatically the needed - * engine because it would not be configured in such stage. - * 2) if you want to pre-configure the engine you will need to set the engine to NULL - * previously and then you could change to the new one without warning/ignoring. - * 3) if you have dedicated message objects for each interface (application id), then + * 1) if you want to reuse the message, as a recommendation, you should #clear the + * message. In that way, next operation will adjust automatically the needed engine. + * 2) if you have dedicated message objects for each interface (application id), then * you could set the corresponding engine on constructor (or setEngine), and forget * about #clear. The needed cleanup will be done automatically from decoding and xml * loading procedures, and initialized engine will be kept along message operations. @@ -756,7 +753,7 @@ public: during hexadecimal read. Normally only printable 'data' fields are used for matching issues. For example, imagine a 'pattern.xml' file like: - + @@ -799,3 +796,4 @@ public: #endif +