Prefer g_seekable_seek() over camel_stream_reset().

When a stream is obviously a file or memory stream (both of which
implement the GSeekable interface), use g_seekable_seek() instead of
camel_stream_reset().

This is helping me discover if it's safe to remove camel_stream_reset().
We want to eventually move to GIO streams, which have no reset method.

1 files changed, 0 insertions, 6 deletions

diff --git a/modules/plugin-mono/Camel.cs b/modules/plugin-mono/Camel.cs
index c415498c02..21fbe468f4 100644
--- a/modules/plugin-mono/Camel.cs
+++ b/modules/plugin-mono/Camel.cs
@@ -630,7 +630,6 @@ namespace Camel {
 		[DllImport("camel-1.2")] static extern int camel_stream_eos(IntPtr o);
 		[DllImport("camel-1.2")] static extern int camel_stream_close(IntPtr o);
 		[DllImport("camel-1.2")] static extern int camel_stream_flush(IntPtr o);
-		[DllImport("camel-1.2")] static extern int camel_stream_reset(IntPtr o);
 
 		public int write(byte [] data, int len) {
 			int ret;
@@ -671,11 +670,6 @@ namespace Camel {
 				throw new Exception(Exception.Type.SYSTEM, "IO close Error");
 		}
 
-		public void reset() {
-			if (camel_stream_reset(cobject) == -1)
-				throw new Exception(Exception.Type.SYSTEM, "IO reset Error");
-		}
-
 		public void flush() {
 			if (camel_stream_flush(cobject) == -1)
 				throw new Exception(Exception.Type.SYSTEM, "IO close Error");