Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 861
    • Issues 861
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 43
    • Merge requests 43
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GLib
  • Issues
  • #720
Closed
Open
Issue created Jun 28, 2013 by Bugzilla@bugzilla-migration💬Reporter

need a way to block on pending async call

Submitted by Allison (desrt)

Link to original bug (#703224)

Description

I've often wanted a way to block on a pending async call.

Of course this is useful for the case of turning an async call into a sync one (using the ages old private maincontext trick). My usecase is different, though: I want to be able to take an async call that was already dispatched and block until it completes.

This is a pretty complicated affair, seeing as the async call could have subcalls inside of it. I think more or less the only way that this could work is to create a private main context from the start and dispatch the call from there. The private context would then need a way of being chained onto the user's main context.

So in effect, this bug is about creating a GSource for GMainContext itself: one that dispatches when the nested maincontext has some work to do.

Assignee
Assign to
Time tracking