huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fixed docs on SocketNodeInstance 

namespace was incorrect
This commit is contained in:
Meir017 2017-11-24 08:41:55 +02:00 committed by Steve Sanderson
parent 18140929e7
commit 02bbcb68f1
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/Microsoft.AspNetCore.NodeServices.Sockets/SocketNodeInstance.cs
View File

@ -14,8 +14,7 @@ namespace Microsoft.AspNetCore.NodeServices.Sockets
/// <summary> /// <summary>
/// A specialisation of the OutOfProcessNodeInstance base class that uses a lightweight binary streaming protocol /// A specialisation of the OutOfProcessNodeInstance base class that uses a lightweight binary streaming protocol
/// to perform RPC invocations. The physical transport is Named Pipes on Windows, or Domain Sockets on Linux/Mac. /// to perform RPC invocations. The physical transport is Named Pipes on Windows, or Domain Sockets on Linux/Mac.
/// For details on the binary streaming protocol, see /// For details on the binary streaming protocol, see <see cref="Microsoft.AspNetCore.NodeServices.Sockets.VirtualConnections.VirtualConnectionClient" />
/// Microsoft.AspNetCore.NodeServices.HostingModels.VirtualConnections.VirtualConnectionClient.
/// The advantage versus using HTTP for RPC is that this is faster (not surprisingly - there's much less overhead /// The advantage versus using HTTP for RPC is that this is faster (not surprisingly - there's much less overhead
/// because we don't need most of the functionality of HTTP. /// because we don't need most of the functionality of HTTP.
/// ///
@ -238,4 +237,4 @@ namespace Microsoft.AspNetCore.NodeServices.Sockets
} }
#pragma warning restore 649 #pragma warning restore 649
} }
} }