Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / codebutler/android-websockets issues and pull requests

#37 - Usage of deprecated library org.apache.http

Issue - State: open - Opened by dllentry about 5 years ago

#36 - Allow case-independent "Sec-WebSocket-Accept"

Pull Request - State: closed - Opened by dengr1065 over 6 years ago

#34 - WebSocket Error when send(String) or send(byte)

Pull Request - State: open - Opened by devxgaming over 6 years ago

#33 - connect to device with 4g active

Issue - State: open - Opened by AhmedX6 about 7 years ago

#32 - deleted deprecated method and change okhttp library , custom library

Pull Request - State: closed - Opened by metamic over 7 years ago

#31 - According to RFC header names are case-insensitive

Pull Request - State: closed - Opened by PawelErnestLuczak almost 8 years ago

#30 - include this package in android studio

Issue - State: closed - Opened by antoniomerlin almost 9 years ago - 1 comment

#28 - multi client

Issue - State: open - Opened by jeilun almost 9 years ago

#27 - WebSocketClient uses BasicNameValuePair which is removed in Android 6.0 SDK

Issue - State: open - Opened by vdesmet93 about 9 years ago - 1 comment

#26 - Socket not connected

Issue - State: closed - Opened by hoangsondev over 9 years ago - 4 comments

#25 - How to check the client isConnected??

Issue - State: open - Opened by dyguests over 9 years ago - 1 comment

#24 - how to send Ping to server

Issue - State: closed - Opened by gedeju over 9 years ago - 2 comments

#23 - Client not seeing the "Sec-WebSocket-Accept" header

Issue - State: open - Opened by raduvarga over 9 years ago

#22 - It says connected but it didnot

Issue - State: open - Opened by weiwei100 over 9 years ago

#20 - NullPointer

Issue - State: open - Opened by aquintiliano over 10 years ago - 1 comment

#19 - Calling disconnect throws exception

Issue - State: open - Opened by Umaid1 over 10 years ago - 6 comments

#18 - Don't catch Exception as it hides any possible cause of trouble in the user code.

Pull Request - State: closed - Opened by ticofab over 10 years ago - 1 comment

#17 - i want to work with you guys

Pull Request - State: closed - Opened by mkiswani over 10 years ago

#16 - Handler-->Listener

Pull Request - State: open - Opened by tianyl1984 almost 11 years ago

#15 - websocketclient.handler can not be resolved

Issue - State: open - Opened by rohitshinde about 11 years ago - 2 comments

#14 - HTTP proxy support

Pull Request - State: open - Opened by c99koder about 11 years ago

#13 - Readme Usage sample bug

Issue - State: open - Opened by andygup about 11 years ago - 1 comment

#12 - 2 cherry picks and a ping bugfix

Pull Request - State: open - Opened by joepadmiraal over 11 years ago

#11 - Namespaces not supported

Issue - State: open - Opened by heartforit over 11 years ago

#10 - Thanks for code. Maybe you interested in proposed improvements:

Issue - State: open - Opened by igor-- over 11 years ago - 8 comments

#9 - wrong close frame status code parsing

Issue - State: open - Opened by osanha over 11 years ago

#8 - added time out to websocketclient

Pull Request - State: open - Opened by blafountain over 11 years ago

#6 - Validate Handshake Response

Pull Request - State: closed - Opened by pkulak almost 12 years ago - 1 comment

#5 - Thread problems with Fragments

Issue - State: closed - Opened by ahornerr almost 12 years ago - 1 comment

#4 - Add TrafficStats socket tagging

Pull Request - State: closed - Opened by c99koder about 12 years ago

#3 - "Expected non-final packet" on fragmented messages

Issue - State: open - Opened by jketterl about 12 years ago - 1 comment

#2 - SSL Support

Issue - State: closed - Opened by unicomp21 over 12 years ago

#1 - Socket.IO support

Pull Request - State: closed - Opened by koush over 12 years ago - 1 comment