I don't view this as a compromise, its actually in favor of Jerome. Let
me reiterate that we're enforcing a streaming model for a performance
optimization that generally will be irrelevant in 95% of applications
and deployments. A model that is at the expense of code readability,
and a model that should become 100% irrelevant as OS's and VM's improve
in the future. If Erlang can do it within-vm, no reason Java can't.
Jerome Louvel wrote:
> Hi Marc,
>
> +1 for me. Time to close indeed.
>
> Best regards,
> Jerome
>
>> -----Message d'origine-----
>> De : Marc.Hadley_at_Sun.COM [mailto:Marc.Hadley_at_Sun.COM]
>> Envoyé : mercredi 12 mars 2008 14:46
>> À : dev_at_jsr311.dev.java.net
>> Objet : Re: JSR311: Response isn't adequate
>>
>> Not wishing to stifle an interesting debate but I'd like to move
>> towards a conclusion ;-). Can we close this issue with the proposal
>> below ? It gets Bill an OutputStream that can be used without having
>> to implement a MessageBodyWriter while not tying up a service thread
>> as desired by Jerome and Stephan. Seems like a reasonable compromise
>> to me.
>>
>> Marc.
>>
>> On Mar 10, 2008, at 3:59 PM, Marc Hadley wrote:
>>> public interface StreamedOutput {
>>> void write(OutputStream o);
>>> }
>>>
>>> Which can be returned when you want to do streaming - the
>> spec would
>>> require implementations to support this type.
>> ---
>> Marc Hadley <marc.hadley at sun.com>
>> CTO Office, Sun Microsystems.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
>> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com