Mailing-List: contact dev-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Developers List" <dev@poi.apache.org>
Date: Fri, 10 Feb 2017 21:01:03 +0000 (GMT)
From: Nick Burch <apache@gagravarr.org>
To: POI Developers List <dev@poi.apache.org>
Subject: RE: NPOIFS, files and the read-only flag
In-Reply-To: <4CBBBDD7FB566C4DB70EB7A04E0B466F012F9FA6@Exchange3.exchange2.metalexmfg.com>
Message-ID: <alpine.DEB.2.11.1702102058230.8418@urchin.earth.li>
References: <4b6e4c68-8bfe-33db-cf66-17c4302401ca@apache.org> <4CBBBDD7FB566C4DB70EB7A04E0B466F012F9FA6@Exchange3.exchange2.metalexmfg.com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
archived-at: Fri, 10 Feb 2017 21:01:18 -0000

On Fri, 10 Feb 2017, Murphy, Mark wrote:
> I guess I don't understand this that well, so please bear with me. With 
> a File loaded read-write how are changes stored such that writing to a 
> different OutputStream is not feasible? I don't think they are written 
> back to the original File until a write operation is performed. Or is 
> that incorrect?

At the NPOIFS level, if you do writes to an open read-write NPOIFS 
instance, those will get reflected back to the original file in 
near-realtime without having to call close/write.

At the HSSF / HWPF / etc level, if you open from a read-write NPOIFS, then 
write out to a new stream, nothing changes on the original file as a new 
NPOIFS is generated + populated.

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org