Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Disconnect calls Connect #31

Open
dabielkabuto opened this issue Jun 20, 2017 · 0 comments
Open

Disconnect calls Connect #31

dabielkabuto opened this issue Jun 20, 2017 · 0 comments

Comments

@dabielkabuto
Copy link

dabielkabuto commented Jun 20, 2017 •
edited
Loading

Thank you for your excellent component. I am not sure if it is a bug or not but when from a client app I call Disconnect(), then Connect is called again from the Queue:
TIdWebsocketQueueThread.Execute
TIdWebsocketQueueThread.ProcessQueue
TIdWebsocketMultiReadThread.PingAllChannels
TIdHTTPWebsocketClient.TryUpgradeToWebsocket
TIdHTTPWebsocketClient.InternalUpgradeToWebsocket
TIdHTTPWebsocketClient.Connect

By the way, destroying the component in the client effectively disconnect from the server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dabielkabuto