directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <ggreg...@seagullsw.com>
Subject RE: [codec] StatefulDecoders
Date Tue, 24 Feb 2004 02:56:06 GMT
>   public java.util.List operation(java.nio.ByteBuffer buffer);

This brings up an interesting issue: How do we potentially package and
deliver some code that depends on Java 1.4. In a second [codec] jar? I think
we should keep the JRE requirement to a minimum for [codec]. Here, we are
stuck on 1.3.1 for the foreseeable future. Some others, I imagine need 1.2
compatibility.

Gary

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Monday, February 23, 2004 18:13
> To: Jakarta Commons Developers List
> Cc: 'Apache Directory Developers List'
> Subject: RE: [codec] StatefulDecoders
> 
> > > I've been working on the idea of stateful Decoders designed for use
> with
> > > non-blocking reads where buffers are read from channels and used by
> > > decoders.
> > > http://nagoya.apache.org/jira/secure/ViewIssue.jspa?id=13599
> 
> > How does your proposal contrast/differs/combines with what has
> > been referred to on this list as "streamable" codecs?
> > See http://issues.apache.org/bugzilla/show_bug.cgi?id=19882
> 
> The streamable decoders have an interface like:
> 
>   public void operation(InputStream in, OutputStream out)
>      throws Exception;
> 
> which means that the calling thread is going to be blocked on I/O, whereas
> Alex's proposed interface is:
> 
>   public java.util.List operation(java.nio.ByteBuffer buffer);
> 
> which is called as data arrives.  The difference is pull-model (blocking
> I/O) vs push-model (non-blocking I/O).
> 
> 	--- Noel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org

Mime
View raw message