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

WebSockets middleware should not replace server implementation #11

Closed
davidfowl opened this issue Jun 30, 2014 · 2 comments
Closed

WebSockets middleware should not replace server implementation #11

davidfowl opened this issue Jun 30, 2014 · 2 comments
Assignees
@Tratcher
Labels
3 - Done bug
Milestone
1.0.0-alpha3

Comments

@davidfowl
Copy link
Member

The websockets middleware should only replace the IHttpWebSocketFeature if there isn't one.
@davidfowl davidfowl added this to the 0.1-alpha3 milestone Jun 30, 2014
@Tratcher
Copy link
Member

The overwrite should be optional. Different implementations will have different features, bugs, perf, etc..

@davidfowl
Copy link
Member Author

Sure maybe a flag to overwrite then.

@Tratcher Tratcher mentioned this issue Jun 30, 2014
Merged
@Tratcher Tratcher closed this as completed Jul 3, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tratcher Tratcher

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0-alpha3
Development

No branches or pull requests
2 participants
@davidfowl @Tratcher