Re: NUBIE API design.
"Toby Hudon" <[email protected]>
| Newsgroups | gmane.comp.multimedia.media-api |
|---|---|
| Message-ID | <[email protected]> |
> > > > Hopefully a frame is a shared pointer, not the whole data :) > > Sorry, that was my point. I was just wondering on how he intended to pass > the data around. If a filter further down the chain changed data in the > frame of a shared pointer, would it screw things if there was an error > somewhere in the chain causing it to need to retransmit data? Yes it was intended as pointers. I don't think this kind of issue would come up, because there should never be a retransmit. Basicly the retries happen on the request (caller's) side, so if there's a problem data isn't transmitted until it's resolved. The object being asked to transmit will just generate explicit fails. If there's some pass-throughs involved, then the explicit fails will pass through, so a filter that wants RGB can ask a subtitle muxer to keep changing the requested colorspace even though it really wants an answer from the codec further up the pipeline. The messages will get passed transparently through the intervening filters and handled as if there was a direct connection between the two concerned. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm