Prev: Applet UpCall from JS Event - Which Thread?
Next: eclipselink @table annotation
From: Mike Schilling on 20 Mar 2010 13:54
dennis wrote:
> Hi Mike,
>
> Thanks for the feedback. I looked into FilterInputStream, but did not
> want to use it while the underlying stream might support seek(),
> mark() and reset() and this will prevent data being written to the
> output or data being written multiple times. You either have to
> handle that or at least mark the output that there was a part not
> written or writtenmore then once. Especially when you use it for
> logging or storing xml-requests.


I must be missing something. Whether you override FilterInpoutStrewam or
not, you still have the ability to override mark(), markSupported(), skip(),
and reset() yourself and do whatever you think is best.


From: Lew on 20 Mar 2010 14:19
dennis wrote:
> - The license issue. If I use mine it will be done under the modified
> BSD-license so no restrictions to future users.

Of what restrictions do you speak? The point of open-source licenses is that
they *remove* restrictions from future users.

The BSD license and the Apache license aren't very far apart in their
consequences.

I really am interested in what negative consequences you anticipate from the
Apache license. What are they?

--
Lew
From: John B. Matthews on 20 Mar 2010 16:28
In article <ho33il$g7e$1(a)news.albasani.net>, Lew <noone(a)lewscanon.com>
wrote:

> dennis wrote:
> > - The license issue. If I use mine it will be done under the modified
> > BSD-license so no restrictions to future users.
>
> Of what restrictions do you speak? The point of open-source licenses
> is that they *remove* restrictions from future users.
>
> The BSD license and the Apache license aren't very far apart in their
> consequences.
>
> I really am interested in what negative consequences you anticipate from the
> Apache license. What are they?

I would like to hear more on this, too. In particular, which modified
BSD-license?

<http://en.wikipedia.org/wiki/BSD_licenses>

--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>
From: dennis on 22 Mar 2010 08:57
Hi Lew,

>Of what restrictions do you speak? The point of open-source licenses is that
>they *remove* restrictions from future users.

>The BSD license and the Apache license aren't very far apart in their
>consequences.

>I really am interested in what negative consequences you anticipate from the
>Apache license. What are they?
>--
>Lew

First let me clarify something. With users in this case I mean people or customers using the sources and not only the compiled code. For the later no real restrictions do apply. For the people using and deriving of the sources restrictions do apply.
The most notable is from the GPL: All derived works should also be open source. http://www.opensource.org/licenses/gpl-2.0.php
The Apache license has just one restriction that has some of my customers worried: If you have a NOTICE in your software and made a derivitive work from any Apache code you have to mention Apache in that notice. http://www.apache.org/licenses/LICENSE-2.0.html
A comparable advertising restriction was in the original license from BSD as well, but was deleted in 1999. Hence the name 'modified' BSD license. Although me stil referring to 'modified' 11 years after it was done, might indicate I'm getting old ;-) http://www.opensource.org/licenses/bsd-license.php

I use some open source software in products I create for my customers. After I leave they should be able to extend or alter the work I have done or the open source software it relies on, without being required to release it as open source or advertise other organisations, not even my own.

Don't get me wrong. I have nothing against Apache, they have some great stuff out there and I use it regularly. If I need to fix something in their code I will supply it back to them for possible commitment in future releases. For my customers it is a different matter. They cannot derive works of it, without complying to the notice part of the license, or supplying it back to Apache. Something they might not be willing to do.

I hope this answers your questions.

Kind regards,
Dennis Groenendijk



From: dennis on 22 Mar 2010 09:02
Hi Mike,

>I must be missing something. Whether you override FilterInpoutStrewam or
>not, you still have the ability to override mark(), markSupported(), skip(),
>and reset() yourself and do whatever you think is best.

Of course I can overwrite FilterInputStreams methods to do whatever I want. InputStream itself however had all the functionality in these methods I needed to make sure all bytes are read and written just once. It was thus more efficient to just use InputStream.

Kind regards,
Dennis
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Applet UpCall from JS Event - Which Thread?
Next: eclipselink @table annotation