dev@grizzly.java.net

RE: Next release: 1.5.1. What do we want?

From: Jerome Louvel <contact_at_noelios.com>
Date: Wed, 16 May 2007 11:52:31 +0200

Hi again,

This was the right track, I was able to get rid of the exception by properly
handling the non blocking socket channel case in our ByteUtils class.

Now, I can return string representations but returning files seems to hang.
This can be reproduced with our tutorial example 06. I'm not sure yet why.
Maybe because we rely on the File.transferTo() method.

Best regards,
Jerome

> -----Message d'origine-----
> De : Jerome Louvel
> Envoyé : mercredi 16 mai 2007 10:19
> À : dev_at_grizzly.dev.java.net
> Objet : RE: Next release: 1.5.1. What do we want?
>
>
> Salut Jean-Francois,
>
> > Quick question (I will install the latest version). Are you
> > changing the channel from non blocking to blocking somewhere:
>
> Not really. I think the issue is coming from the
> org.restlet.util.ByteUtils class which uses the NIO's
> Channels.newOutputStream(writableChannel) method. But this
> method only works for blocking NIO channels...
>
> I will try to change the implementation to take into account
> non blocking socket channels.
>
> Best regards,
> Jerome
>