Moin Frank,

Am Donnerstag, den 28.08.2008, 21:29 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
> 
> > This *may* be something like the documentation bug there was talk about
> > once upon a time. You wrote:
> > 
> > <cite>
> > Hi Matthias,
> > 
> >> ....
> >> The only conclusion I can draw from such an inconsistent API is that any
> >> implementation that claims to be usable can only ignore the 'Length'
> >> argument.
> 
> I wrote that, really? Sounds like I knew what I was talking about back
> then :)

:D

> >> ....
> >> Probably only 'setBinaryStream()' documentation (and implementation?)
> >> need to be fixed to clarify 'Length' as 'Limit'.
> > 
> > I fully agree, and I'll file an issue to adjust the documentation as
> > well as the implementations.
> 
> Thanks. If you could refer to this old discussion and the reasoning
> therein, this could be helpful.
> 
> I in fact looked up the implementation before I answered to Fernand, and
> we use the length as length currently, not as limit.

I hope your workload will lower soon. In fact the statement "I'll file
an issue ..." is part of the citation. ;)

But I'd take that task if I am sure what to write. Is it a limit or a
lenght for:

   Form.Columns.getByName("").setBinarySream()
   aka ResultSet.get/setAnything.setBinaryStream()

   Form.Columns.getByName("").updateBinaryStream()
   aka ResultSet.get/setAnything.updateBinaryStream()

   css.sdbc.XParameter.setBinaryStream()

?

And I'll try again:

Does the last of those three (or all at best) need a stream implementing
css.io.XSeekable besides the XInputStream/XOutputSream interface?

The same is true for the ComponentLoader (not Documentloader) for input
streams, which is why people have to implement a stream wrapper offering
both interfaces (XInputStream & XSeekable).

Since my experiments handing over an input stream to a XParameter are
all blocking except when a dbase db is used as backend this could be the
problem. Or the "length" argument is biting back ...

Marc



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to