🚀 go-pugleaf

Regis Eloi wrote:
> 
> William Yu wrote:
> >
> > The above works great -- except for one issue. If the compression buffer
> > is not filled, objects sit in the write queue. Any insight on the next
> > logical step?
> 
> I think you have to call the flush method on your streams.
> Something like:
> zip_out.flush();

No dice. This was one of the first commands I tried and absolutely
nothing happens. If you look at the API documentation, you will notice
that flush is not listed under methods -- it's probably overridden to do
nothing since flushing the output buffer before the zip streams have a
chance to compress the buffer would cause some problems.

The finish() method does work -- but it closes up all the resources and
you can't use the stream anymore.

Hmmm, I suppose I could open & close the Zip & Object streams for every
discrete operation. I'm going to need a network traffic analyzer to see
what type of bandwidth this would suck up.