[Mono-bugs] [Bug 74878][Nor] Changed - Defining more than one formatter in remoting channel not supported

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Dec 2 21:12:46 EST 2005

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 robertj at gmx.net.


--- shadow/74878	2005-12-02 20:14:20.000000000 -0500
+++ shadow/74878.tmp.20582	2005-12-02 21:12:46.000000000 -0500
@@ -183,6 +183,17 @@
 The patch looks correct. However, it is a potentially breaking change
 and I'd like some tests to be done before committing, to make sure
 that MS.NET behaves in the same way. For example, how does react
 MS.NET when it receives a request in the TCP channel which does not
 include the content type header?. With your patch Mono would crash, I
 just want to make sure MS.NET does the same.
+------- Additional Comments From robertj at gmx.net  2005-12-02 21:12 -------
+I don't want to have this commited in rush, just wanted to know
+if I'm on the right way.
+There is still an issue with async calls and the patch,
+probably because the mono formatter's ProcessMessage
+doesn't deal with ServerProcessing.Async.
+BTW, would you please have a look at #76809 ?

More information about the mono-bugs mailing list