-
Notifications
You must be signed in to change notification settings - Fork 535
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
Create connect()
and disconnect()
#9168
Comments
connect()
and disconnect()
on Container
setAutoReconnect()
to remove immediate connection/disconnect logic
setAutoReconnect()
to remove immediate connection/disconnect logicconnect()
and disconnect()
on Container
@scottn12 - I believe manual connect/disconnect capability already exists, as |
@markfields, I had initially planned for these APIs to have slightly different functionality. However, based on the latest design discussions in #8745, I believe these functions are going to be more about API naming as you alluded to. I will be sure to update the description of this issue once we get a bit more clarification! |
connect()
and disconnect()
on Container
connect()
and disconnect()
on Container
connect()
and disconnect()
on Container
connect()
and disconnect()
on Container
FYI, this issue has been updated to reflect the changes in #8745 |
connect()
and disconnect()
on Container
connect()
and disconnect()
As described in #8745,
Container.connect()
andContainer.disconnect()
will be introduced to provide developer-friendly APIs to control the connection state of a container. The functionality ofconnect()
will be similar to the currentContainer.resume()
(will be deprecated in #9167).disconnect()
will have simlar functionality to the currentContainer.setAutoReconnect(false)
API call (also deprecated in #9167).Phases:
connect()
anddisconnect()
toContainer
andIContainer
#9744connect()
anddisconnect()
toIFluidContainer
#9745connect()
anddisconnect()
#9746connect()
/disconnect()
mandatory onIContainer
andIFluidContainer
#9945disconnect()
is called while the container is attempting to connect #9789The text was updated successfully, but these errors were encountered: