Rearchitected the way GMimeObject's process added/removed headers

This now works based on an event system similar to MimeKit's

Headers get added/removed/set on the GMimeHeaderList directly
which then emits a 'changed' event that GMimeObject listens
to and dispatches appropriately to header_added(), header_changed(),
header_removed(), or headers_cleared().

These virtual methods are where the work now gets done to update
the object's parsed representation of various headers.

1 files changed, 5 insertions, 6 deletions

diff --git a/PORTING b/PORTING
index 4669de7d..f25c1992 100644
--- a/PORTING
+++ b/PORTING
@@ -43,12 +43,11 @@ Porting from GMime 2.6 to GMime 3.0
   decoder API's take a GMimeParserOptions argument that allows for
   specifying fallback charsets.
 
-- GMimeObject's prepend_header(), append_header(), and set_header() virtual
-  methods now all take a const char *raw_value and gint64 offset arguments.
-  The raw_value is the raw header value cloned exactly as the parser found
-  it in the stream (meaning it retains the original folding). The 'value'
-  argument remains as it has always been, an unfolded (but still encoded)
-  header value.
+- GMimeObject's prepend_header(), append_header(), set_header(), get_header(),
+  and remove_header() virtual methods have all been removed. They have been
+  replaced by the header_added(), header_changed(), header_removed(), and
+  headers_cleared() virtual methods to allow users to set headers on the
+  GMimeHeaderList directly and still get notifications of those changes.
 
 - g_mime_object_new() and g_mime_object_new_with_type() both now take a
   GMimeParserOptions argument.