Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Move Sockets.Abstractions to System.IO.Pipelines #615

Closed
1 task done
davidfowl opened this issue Jun 29, 2017 · 0 comments
Closed
1 task done

Move Sockets.Abstractions to System.IO.Pipelines #615

davidfowl opened this issue Jun 29, 2017 · 0 comments

Comments

@davidfowl
Copy link
Member

davidfowl commented Jun 29, 2017

Today we're using System.IO.Channels as the server side abstraction but there are some fundamental problems around buffer pooling and memory management. We basically are unable to safely use pooled buffers today since we don't know when we should dispose them. Pipelines solves this issue with a few caveats:

  • - We need to support multiple producers writing to the same socket (in SignalR). (supported with f21f503)
@davidfowl davidfowl added this to the 2.1.0-preview1 milestone Jun 29, 2017
@davidfowl davidfowl self-assigned this Jun 29, 2017
@muratg muratg modified the milestones: 2.1.0-preview1, 1.0.0-alpha1 Aug 18, 2017
@muratg muratg mentioned this issue Dec 2, 2017
55 tasks
@analogrelay analogrelay assigned analogrelay and unassigned davidfowl Dec 6, 2017
@davidfowl davidfowl assigned davidfowl and unassigned analogrelay Feb 7, 2018
davidfowl added a commit that referenced this issue Feb 10, 2018
- Change the Sockets abstraction from Channel<byte[]> to pipelines.

#615
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants