After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703224 - need a way to block on pending async call
need a way to block on pending async call
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: mainloop
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-06-28 01:52 UTC by Allison Karlitskaya (desrt)
Modified: 2018-05-24 15:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Allison Karlitskaya (desrt) 2013-06-28 01:52:18 UTC
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.
Comment 1 Dan Winship 2013-06-28 12:34:12 UTC
somewhat related to bug 690126
Comment 2 GNOME Infrastructure Team 2018-05-24 15:28:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/720.