9 commits

Author	SHA1	Message	Date
Guus der Kinderen	3f13d90a56	Websocket implicit discovery should use common ports ... When enabled, the websocket implementation will attempt to use two implicit endpoints, using these URLs: - `wss://[host]:5443/ws` - `ws://[host]:5443/ws` These endpoints should include ports that are used by default by known implementations, such as 5280/5281 (Prosody) and 7070/7443 (Openfire).	2023-01-19 13:09:20 +01:00
Florian Schmaus	aefbb28875	[websocket] Fix getStreamFromOpenElement()	2021-04-01 17:43:07 +02:00
Florian Schmaus	4aacdc5154	Add smack-websocket-java11 ... This also lifts a bunch of logic from smack-websocket-okhttp into smack-websocket. Furthermore, the following subprojects require now Java 11: - smack-integration-test - smack-omemo-signal-integration-test - smack-repl - smack-websocket-java11 Related tracking issue: SMACK-835	2021-02-14 20:34:40 +01:00
Florian Schmaus	a7b3303f3e	Bump ErrorProne to 2.5.1 and refactor Providers a bit ... This also resulted in a refactoring of the Providers and parsing Exceptions. NumberFormatException and ParseException can now be thrown directly, the wrapping in a SmackParsingException is down at a higher layer, i.e. in AbstractProvider.	2021-01-29 09:26:15 +01:00
Aditya Borikar	1df0763f92	Remove AbstractWebsocketNonza since it is no longer needed	2021-01-25 20:31:51 +01:00
Florian Schmaus	c5a546554b	Rework WebSocket code ... Related to SMACK-835.	2021-01-25 19:56:54 +01:00
Florian Schmaus	9002be8e7a	s/Websocket/WebSocket/ ... Java SE as well as OkHttp use 'WebSocket' (not 'Websocket'). Let us do the same. SMACK-835.	2020-09-01 21:47:36 +02:00
Florian Schmaus	6533cb7ed1	Introduce smack-websocket-okhttp ... This uses Java's Service Provider Interface (SPI) to abstract different WebSocket implementations. SMACK-835	2020-09-01 21:36:13 +02:00
adiaholic	7ed29b9d5f	Introduce websocket module into smack	2020-08-28 23:40:40 +05:30