[Mono-bugs] [Bug 58853][Wis] Changed - [System.Runtime.Serialization.Formatters.Soap] Soap writer/reader don't support headers

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by totte@hiddenpeaks.com.

http://bugzilla.ximian.com/show_bug.cgi?id=58853

--- shadow/58853	2004-05-22 10:19:23.000000000 -0400
+++ shadow/58853.tmp.12081	2004-05-22 10:42:28.000000000 -0400
@@ -2,21 +2,20 @@
 Product: Mono: Class Libraries
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: totte@hiddenpeaks.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
-Cc: 
 Summary: [System.Runtime.Serialization.Formatters.Soap] Soap writer/reader don't support headers
 
 The SoapFormater doesn't support headers (SOAP:Header) and therefore it's 
 currently impossible to implement CallContext for Http remoting channel.
 
 When using SoapFormater:Serialize(stream, graph, headers) headers are 
@@ -24,6 +23,17 @@
 System.Runtime.Remoting.Header in the header array.
 
 Same goes for Deserialize that should call HeaderHandler for each soap 
 header found.
 
 (this is in wrong section (corlib))
+
+------- Additional Comments From totte@hiddenpeaks.com  2004-05-22 10:42 -------
+The HeaderHandler support is complex, it allows callers to send in a 
+HeaderHandler that returns a IFieldInfo object that is called to 
+get/read the serialized information.
+
+This is used by MS to create a empty MethodResponse and pass in the 
+MethodResponse.HeaderHandler and get a initialized object back 
+(ignoring the return object)
+
+Lluis, anything we can reuse from our binary serializer?