[Bug 794153] GstPromise is weird

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=794153

--- Comment #3 from Matthew Waters (ystreet00) <ystreet00 at gmail.com> ---
(In reply to Jan Alexander Steffens (heftig) from comment #2)
> > Nothing forces you to have strings for values.
> 
> I mean the structure has a name itself as well as a map of string keys to
> GValues.

Right. These names can mean whatever you want them to mean if anything.

> > Already the case for interrupt. Expiration is the other way around and signals that a value will never be produced to avoid pesky deadlocks waiting for a promise.
> 
> So EXPIRED was meant for the producer to notify a consumer that there won't
> be a reply? Why not use a reply for this as well?

Not the producer but something else that does not know anything about expected
values exchanged.  A reply could be constructed but then that specific reply
could never be used for a real value.

> > The consumer can signal INTERRUPTED for saying it doesn't want the producer (promiser) to produce the result anymore.
> 
> The producer needs to poll for this signal by checking the promise result.
> There's only one callback on the promise for use by the consumer.

Yes. In some way that is specific to the value to be produced.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.