Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of jak-commons-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@commons.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: [io?] [all] flexible "char-array" ?
Date: Wed, 08 Apr 2009 11:36:05 +0200
Lines: 32
Message-ID: <grhr4i$u87$1@ger.gmane.org>
References: <8831CCE6-AD06-4007-9763-AC1D1CEB9C34@activemath.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/0.10.9
Sender: news <news@ger.gmane.org>

Paul Libbrecht wrote at Mittwoch, 8. April 2009 11:17:

> 
> Hello commons list,
> 
> one thing I keep seeing around is people exchanging either too big
> strings, byte-arrays, or stringbuffers. It looks like, they one has
> still not found something sensible that describes something close to
> an array of characters so:
> 
> - that can give its length
> - that can be read and re-read
> - with a variant can be  changed to (e.g. with a writer)
> 
> but something that is flexible enough so that:
> 
> - it does not reserve a block of contiguous bytes in RAM!
> - it scales pretty big
> - maybe it even has regions mapped into file
> 
> where should I look for such a family of objects?
> Commons-IO could be such maybe?
> 
> paul
> 
> PS: last I looked, many many many people serialize massive document as
> XML, that is good, but they exchange that XML as string!

Have a look at the different ImageInputStream/ImageOutputStream
implementations. In fact, they don't have to be used for images only ;-)

- Jörg


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