mirror of
https://github.com/vanitasvitae/Smack.git
synced 2025-09-09 09:09:38 +02:00
Fixes spelling (includes one API change)
Mostly benign changes. Added one new method to replace a method with a spelling mistake in its name. Kept the old method, marked as 'deprecated'.
This commit is contained in:
parent
38c6dd21b4
commit
c85bcadd81
140 changed files with 270 additions and 265 deletions
|
@ -51,7 +51,7 @@ public final class WebSocketConnectionAttemptState {
|
|||
/**
|
||||
* Establish a websocket connection with one of the discoveredRemoteConnectionEndpoints.<br>
|
||||
*
|
||||
* @return {@link AbstractWebSocket} with which connection is establised
|
||||
* @return {@link AbstractWebSocket} with which connection is established
|
||||
* @throws InterruptedException if the calling thread was interrupted
|
||||
*/
|
||||
@SuppressWarnings({"incomplete-switch", "MissingCasesInEnumSwitch"})
|
||||
|
|
|
@ -135,7 +135,7 @@ public final class XmppWebSocketTransportModule
|
|||
|
||||
// TODO: It appears this should be done in a generic way. I'd assume we always
|
||||
// have to wait for stream features after the connection was established. But I
|
||||
// am not yet 100% positive that this is the case for every transport. Hence keep it here for now(?).
|
||||
// am not yet 100% positive that this is the case for every transport. Hence, keep it here for now(?).
|
||||
// See also similar comment in XmppTcpTransportModule.
|
||||
// Maybe move this into ConnectedButUnauthenticated state's transitionInto() method? That seems to be the
|
||||
// right place.
|
||||
|
@ -157,7 +157,7 @@ public final class XmppWebSocketTransportModule
|
|||
final WebSocketRemoteConnectionEndpoint connectedEndpoint;
|
||||
|
||||
public WebSocketConnectedResult(WebSocketRemoteConnectionEndpoint connectedEndpoint) {
|
||||
super("WebSocket connection establised with endpoint: " + connectedEndpoint);
|
||||
super("WebSocket connection established with endpoint: " + connectedEndpoint);
|
||||
this.connectedEndpoint = connectedEndpoint;
|
||||
}
|
||||
}
|
||||
|
|
|
@ -77,7 +77,7 @@ public final class WebSocketRemoteConnectionEndpointLookup {
|
|||
|
||||
public Result(List<RemoteConnectionEndpointLookupFailure> lookupFailures) {
|
||||
// The list of endpoints needs to be mutable, because maybe a user supplied endpoint will be added to it.
|
||||
// Hence we do not use Collections.emptyList() as argument for the discovered endpoints.
|
||||
// Hence, we do not use Collections.emptyList() as argument for the discovered endpoints.
|
||||
this(new ArrayList<>(1), new ArrayList<>(1), lookupFailures);
|
||||
}
|
||||
|
||||
|
@ -99,7 +99,7 @@ public final class WebSocketRemoteConnectionEndpointLookup {
|
|||
|
||||
// TODO: Remove the following methods since the fields are already public? Or make the fields private and use
|
||||
// the methods? I tend to remove the methods, as their method name is pretty long. But OTOH the fields reference
|
||||
// mutable datastructes, which is uncommon to be public.
|
||||
// mutable datastructures, which is uncommon to be public.
|
||||
public List<SecureWebSocketRemoteConnectionEndpoint> getDiscoveredSecureRemoteConnectionEndpoints() {
|
||||
return discoveredSecureEndpoints;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue