OPENCHESSBOARD_WiFi icon indicating copy to clipboard operation
OPENCHESSBOARD_WiFi copied to clipboard

Lichess. How close the connection?

Open 9acca9 opened this issue 3 years ago • 1 comments

Hi. This is a question, not openchessboard. Maybe you can help me. Im using berserk to manage the lichess api. I want to cancel a seek i create. How i can do that? In the lichess api reference says this:

Keep the connection open to keep the seek active.

If the client closes the connection, the seek is canceled. This way, if the client terminates, the user won't be paired in a game they wouldn't play. When the seek is accepted, or expires, the server closes the connection.

But, how close the connection? Dont find anything, probably is too obvius and im ignorant. im using berserk.

Thanks!

9acca9 avatar Sep 12 '22 20:09 9acca9

Hi there,

it depends on your http client implementation. How do you connect to the Lichess API? Most client implementation have a close in method like "yourclientclass.close()"

Alternatively you can explicitly close the connection by sending a request including headers={'Connection':'close'}

Hope that helps. All the best, Timo

9acca9 @.***> schrieb am Mo., 12. Sept. 2022, 22:48:

Hi. This is a question, not openchessboard. Maybe you can help me. Im using berserk to manage the lichess api. I want to cancel a seek i create. How i can do that? In the lichess api reference says this:

Keep the connection open to keep the seek active.

If the client closes the connection, the seek is canceled. This way, if the client terminates, the user won't be paired in a game they wouldn't play. When the seek is accepted, or expires, the server closes the connection.

But, how close the connection? Dont find anything, probably is too obvius and im ignorant. im using berserk.

Thanks!

— Reply to this email directly, view it on GitHub https://github.com/TimoKropp/OPENCHESSBOARD/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLNAF3B6VA5QWFIKMFK4E3V56JIFANCNFSM6AAAAAAQK2K34A . You are receiving this because you are subscribed to this thread.Message ID: @.***>

TimoKropp avatar Sep 13 '22 05:09 TimoKropp