gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash/server/asobj NetStream.cpp NetStream.h


From: Sandro Santilli
Subject: Re: [Gnash-commit] gnash/server/asobj NetStream.cpp NetStream.h
Date: Wed, 30 May 2007 14:55:27 +0200

On Wed, May 30, 2007 at 02:35:09PM +0200, Tomas Groth wrote:
> 
> --- Sandro Santilli <address@hidden> skrev:
> 
> > On Wed, May 30, 2007 at 12:58:36PM +0200, Tomas Groth wrote:
> > > 
> > > --- Sandro Santilli <address@hidden> skrev:
> > > 
> > > > Meanwhile, about DATA -> parser -> decoder
> > > > 
> > > > What's the *Buffer* ?
> > > > 
> > > > Is it the result of the "parsing"  step ?
> > > > 
> > > As it is defined in the current implementation (unless it has changed more
> > than
> > > i've noticed), it is the amount of data available for the parser and
> > thereby
> > > also available for decoding. The interface to the data is through the
> > parser
> > > and/or LoadThread.
> > 
> > So that's LoadThread::getBytesLoaded ?
> > 
> If by that you mean if there is a way to get to know how much data is loaded,
> then yes.

I mean that the Flash platform has the concept of a NetStream Buffer that fills
and flushes and I'm trying to understand how is this modeled in Gnash.

A thread should be fillign the buffer, and another thread should be flushing
it (by displaying portions of it).

LoadThread::getBytesLoaded() is likely *not* this buffer, for a couple of 
reasons:

        1) Can't be misured with "time" units (just bytes)
        2) Never flushes

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]