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.

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

Handling fast connection close #146

Merged
merged 1 commit into from Jan 16, 2015

Conversation

hyades
Copy link
Member

@hyades hyades commented Jan 16, 2015

@mithro The problem if the API calls a method on the server the process is like -

  1. Server is running....
  2. API makes connection
  3. Server registers the API client (unknown role). This will involve the server querying the client over dbus for its role.
  4. API queries server with some dbus method.
  5. API closes connection.

Step 3 and Step (4 followed by 5) can happen in different orders since they occur on separate processes.
Since the registering processes in the server are callbacks, and the connection may die out before the server actually registers it.

@hyades
Copy link
Member Author

hyades commented Jan 16, 2015

https://github.com/timvideos/gst-switch/issues/143 will not fail if there is a time.sleep(1) as the last line.

@landscape-bot
Copy link

Code Health
Code quality remained the same when pulling 948d4c9 on hyades:dbus-connection-issue into 67133aa on timvideos:master.

@mithro mithro added this to the At TimVideos Sprints & LCA milestone Jan 16, 2015
mithro added a commit that referenced this pull request Jan 16, 2015
@mithro mithro merged commit 07f0fc9 into timvideos:master Jan 16, 2015
@mithro mithro deleted the dbus-connection-issue branch January 16, 2015 05:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants