Mailing-List: contact doxia-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: doxia-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: =?iso-8859-1?q?Herv=E9_BOUTEMY?= <herve.boutemy@free.fr>
To: doxia-dev@maven.apache.org
Subject: Re: (output) encoding support in doxia-sink-api
Date: Fri, 7 Nov 2008 17:57:30 +0100
User-Agent: KMail/1.9.10
References: <200811071345.00920.herve.boutemy@free.fr>
 <4914506D.1080808@udo.edu>
In-Reply-To: <4914506D.1080808@udo.edu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200811071757.30370.herve.boutemy@free.fr>

Le vendredi 07 novembre 2008, Benjamin Bentmann a =E9crit :
> It might however be convenient to create an AbstractTextSinkFactory from
> which all/most text-based sinks could inherit.
Seems a good idea.
This would ensure too that every text-based sinks have the same default=20
encoding: it gives some consistency. Is it too limitating? I don't think.

> > Or if we want an API without filename, this method could be transformed
> > into Sink createSink( OutputStream output ) + Sink createSink(
> > OutputStream output, String encoding ).
>
> Unless we actually have need for this (testing with in-memory streams?),
if we want to generate and zip or transfer on-the-fly, for example. It's on=
ly=20
an general idea: I don't really have any plans. I was just guessing that if=
 a=20
method with a Writer was added, some had something in mind.

> I would keep the interface slim to ease its implementation.
ok with that

> Another question might be: Does the relation
>    1 sink -> 1 output file/stream
> always hold or are there formats that might need to output multiple
> files? In the later case, createSink( OutputStream ) would be troublesome.
AFAIK, we always have 1 sink -> 1 file/stream
but I don't have sufficient experience with Doxia use-cases to affirm that.

>
>
> Benjamin
thanks for your comments

Herv=E9