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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79730 --- shadow/79730 2006-10-23 18:57:37.000000000 -0400 +++ shadow/79730.tmp.6728 2006-10-23 18:57:37.000000000 -0400 @@ -0,0 +1,66 @@ +Bug#: 79730 +Product: Mono: Runtime +Version: 1.1 +OS: GNU/Linux [Other] +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Minor +Component: remoting +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Summary: Runtime alters sink stack when creating channel + +Description of Problem: +ChannelServices.CreateServerChannelSinkChain alters the sink stack when it +creates a new channel by appending a provider for the dispatch sink, which +.NET does not do. This means that creating a second channel with the same +sink chain will fail. The last provider must be re-created to work around this. + +Steps to reproduce the problem: +Build and run the following code, with -r:System.Runtime.Remoting: + +-------- +using System; +using System.Collections.Specialized; +using System.Runtime.Remoting; +using System.Runtime.Remoting.Channels; +using System.Runtime.Remoting.Channels.Tcp; + +namespace Test { + class TestClass { + static void Main() { + BinaryServerFormatterSinkProvider provider = new +BinaryServerFormatterSinkProvider(); + + Console.WriteLine( "Next property is {0}", (provider.Next == +null) ? "null" : "not null" ); + + ListDictionary list = new ListDictionary(); + list.Add( "name", string.Empty ); + list.Add( "port", 8080 ); + + new TcpServerChannel( list, provider ); + + Console.WriteLine( "Next property is {0}", (provider.Next == +null) ? "null" : "not null" ); + } + } +} +-------- + + +Actual Results: +Next property is null +Next property is not null + +Expected Results (.NET 2.0): +Next property is null +Next property is null + +How often does this happen? +Every time. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
