Silly question
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- networking
Research direction
Start with the NativeWebSocket.WebSocket.SendText stack trace and the WebGL connection code reported in HTML.framework.js, including _WebSocketConnect. Reproduce two connections to ports 9000 and 9001, then determine whether both reach the open state and accept text sends without the UTF-8 or invalid-state errors.
Written by the indexing model from the issue text.
Description
EDIT: I am using two different instances of the websockt. (So I am not trying to use the same socket to connect twice)
Can the native websocket have two seperate sockets open in a program.
I want to connect to a server using IP:9000
and then a different piece of code needs to connect to the same IP:9001.
All platforms seem to work except for webgl.
Am I missing something?
in flight at once, probably just doing extra work
printErr @ HTML.loader.js:80
HTML.framework.js:1784 Joining game ID 9001
HTML.framework.js:1775 WebSocketInvalidStateException: WebSocket is not in open state.
at NativeWebSocket.WebSocket.SendText (System.String message) [0x00000] in <00000000000000000000000000000000>:0
HTML.framework.js:2766 WebSocket connection to 'ws://71.44.212.56:9001/' failed: Could not decode a text frame as UTF-8.
_WebSocketConnect @ HTML.framework.js:2766
HTML.framework.js:1784 Joining game ID 9001
HTML.framework.js:1775 WebSocketInvalidStateException: WebSocket is not in open state.
at NativeWebSocket.WebSocket.SendText (System.String message) [0x00000] in <00000000000000000000000000000000>:0
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from endel/NativeWebSocket
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
endel/NativeWebSocket#107 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
endel/NativeWebSocket#102 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
endel/NativeWebSocket#101 · 6 comments · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
endel/NativeWebSocket#95 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
endel/NativeWebSocket#94 · 2 comments ·
All issues in endel/NativeWebSocket
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·