Hate them all but nothing good pops to mind right now.  Frankly, I find the 
"streams" in java  8 a confusing term.  When I looked at it I was reminded of 
Cocoon pipelines. I wish they had used that term instead.

Sent from my iPad

> On Sep 2, 2014, at 7:35 PM, Gary Gregory <[email protected]> wrote:
> 
> Yeah, plain 'streams' is not great. Let's see... we are talking about java.io 
> classes that are OutputStreams, InputStreams, Writers, and Readers.
> 
> - log4j-java.io
>    Can you have a . in a module name like that without causing confusion, it 
> kinda looks weird but it the best IMO.
> - log4j-javaio
> - log4j-javaio-bridge
> 
> ?
> 
> Gary
> 
> 
>> On Tue, Sep 2, 2014 at 10:02 PM, Matt Sicker <[email protected]> wrote:
>> Using the name "streams" might be confusing the Java 1.8 streams (aka lazily 
>> evaluated functions/map-reduce). I'd almost suggest javaio or jio or 
>> something similar to emphasise the compatibility.
>> 
>> 
>>> On 2 September 2014 09:22, Gary Gregory <[email protected]> wrote:
>>> Should the new module name/ID be:
>>> 
>>> - log4j-streams
>>> - log4j-streaming
>>> - log4j-<your suggestion>
>>> 
>>> ?
>>> 
>>> Gary
>>> 
>>> -- 
>>> E-Mail: [email protected] | [email protected] 
>>> Java Persistence with Hibernate, Second Edition
>>> JUnit in Action, Second Edition
>>> Spring Batch in Action
>>> Blog: http://garygregory.wordpress.com 
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>> 
>> 
>> 
>> -- 
>> Matt Sicker <[email protected]>
> 
> 
> 
> -- 
> E-Mail: [email protected] | [email protected] 
> Java Persistence with Hibernate, Second Edition
> JUnit in Action, Second Edition
> Spring Batch in Action
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

Reply via email to