Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
References: <CAJm2B-kT-Czp_XVODiPjXrt=UeVTnKxGWS7fDxTaXu7YSE8vBw@mail.gmail.com>
 <CAB917RJOPV5XiCMS2gWRrD8Ptt5gqZHJKTkF5+WB-pbC7M3nEQ@mail.gmail.com> <CAOGo0VYCjFpq_gSCh7iVeu4oZgRkrW3bGGt8km3Eg+fRVk6ATg@mail.gmail.com>
In-Reply-To: <CAOGo0VYCjFpq_gSCh7iVeu4oZgRkrW3bGGt8km3Eg+fRVk6ATg@mail.gmail.com>
From: Benedikt Ritter <beneritter@gmail.com>
Date: Sat, 03 Sep 2016 16:38:15 +0000
Message-ID: <CAB917R+K1ypYJ7GwrHux4tFojtBOKHK1y9F5LWWner4mbHY6-w@mail.gmail.com>
Subject: Re: Back to contributing to Commons Imaging
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c19437e6e3bbc053b9d13aa
archived-at: Sat, 03 Sep 2016 16:38:31 -0000

--94eb2c19437e6e3bbc053b9d13aa
Content-Type: text/plain; charset=UTF-8

sebb <sebbaz@gmail.com> schrieb am Sa., 3. Sep. 2016 um 15:29 Uhr:

> On 3 September 2016 at 13:14, Benedikt Ritter <britter@apache.org> wrote:
> > Hi Damjan,
> >
> > nice you're back. I think there is only one thing left before 1.0 can ne
> > released and that is the findbugs violations. They are mainly about
> > exposure of internal state because the public API accepts byte arrays as
> > input parameter. An easy way to fix this would be to copy the arrays.
> But I
> > think that would be very bad for Performance...
>
> On the other hand, if the existing API is kept, it's not going to be
> possible to easily change the design without breaking compatibility.
>
> The more internal state is exposed, the harder it is to change code in
> the future.
> And the harder it is to fully test the code.
>
> I've not looked at the code recently, but would it be possible to wrap
> the byte array in an object, and only provide access via methods?
>

Could you elaborate some more how that would like? If users have to create
the wrapper object they would still have the reference to the byte array
passed to the wrapper.


>
> It would be fairly easy to replace individual entry reads and writes
> with getters and setters, but that might be too expensive for some
> operations.
> Depending on how many other such operations there are it might be
> possible to provide other methods for them.
>
> > Regards,
> > Benedikt
> >
> > Damjan Jovanovic <damjan@apache.org> schrieb am Sa., 3. Sep. 2016 um
> 11:42:
> >
> >> Hi
> >>
> >> I am back to contributing to Commons Imaging.
> >>
> >> Will start with some cleanups, like try-with-resources instead of
> >> IoUtils.closeQuietly().
> >>
> >> Java and Maven are a heaven send after working in C++ and make with
> Apache
> >> OpenOffice.
> >>
> >> Regards
> >> Damjan
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

--94eb2c19437e6e3bbc053b9d13aa--