-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add WS station fetcher #135
Conversation
…y to fix simplePositioner cursedness with threading
9c140bf
to
affe45c
Compare
build.gradle
Outdated
|
||
// Websocket client libs | ||
compileOnly 'jakarta.websocket:jakarta.websocket-client-api:2.2.0-M1' | ||
implementation 'org.glassfish.tyrus.bundles:tyrus-standalone-client:2.2.0-M1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this dependency provide?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It adds implementation for some jakarta classes, I've replaced it with the jersey one to make it more in line with the impl's we are using for our ws server
is more in line with what we use for our server impl
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When (invalid) mac (not mapped to team) is received over ws connection, telraam resets websocket connection and asks for same detection again -> error loop.
adds another fetcher for the stations, the new one uses websockets to connect to the station.
Telraam chooses the right fetcher based on the scheme of the URL defined in the DB.
I've found out the simplePositioner is not a fan of the multi threading and start panicking with out-of-bound errors after some data has been put in its list. I've opened a new issue as this is something out of scope for this PR
closes #127