2009-08-26 Atsushi Enomoto <atsushi@ximian.com>
commit44bfca7be090608a52abe2e47bbc5655645c8c40
authoratsushi <atsushi@e3ebcda4-bce8-0310-ba0a-eca2169e7518>
Wed, 26 Aug 2009 07:16:25 +0000 (26 07:16 +0000)
committeratsushi <atsushi@e3ebcda4-bce8-0310-ba0a-eca2169e7518>
Wed, 26 Aug 2009 07:16:25 +0000 (26 07:16 +0000)
treecd12919a7323f777987a8256b2fe281d7229d5c5
parent56f2ea54250ea39baf00947f7d3ae78a3d13a936
2009-08-26  Atsushi Enomoto  <atsushi@ximian.com>

* PeerNode.cs : use ulong as same as Welcome message value.

* PeerDuplexChannel.cs : in the Welcome response, return the NodeId
  of the receiver, not the requestor. It resolved the issue that
  .NET client didn't send further messages to mono server.

git-svn-id: svn+ssh://mono-cvs.ximian.com/source/trunk/mcs@140693 e3ebcda4-bce8-0310-ba0a-eca2169e7518
class/System.ServiceModel/System.ServiceModel.Channels/ChangeLog
class/System.ServiceModel/System.ServiceModel.Channels/PeerDuplexChannel.cs
class/System.ServiceModel/System.ServiceModel/ChangeLog
class/System.ServiceModel/System.ServiceModel/PeerNode.cs