-
Notifications
You must be signed in to change notification settings - Fork 248
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
Client opens connection on send - impossible to connect and listen without sending #1
Comments
I wanted to make the connecting lazy... I could add a connect in the receive-method as well. Do you need to be able to connect preemptively as well? |
I am not sure. |
I tried adding a connect on receive. That would solve the use case of listening directly after instantiation. |
Have you tried my patch, and did this solve your problem? |
Yes, it did. Thanks! |
Fixed in #7. |
the call to Client::connect() is made only in Base::send(), which means you need to send() before you can receive().
Would it maybe be feasible, to add the call to Client::connect() in the Client::__construct() function, which would cause the client to connect immediately?
The text was updated successfully, but these errors were encountered: