Cezar Totth wrote:
>
> Hi Jon,
>
> I agree with your point of view, considering these assumptions:
> - user can't know in advance how big the size of response is
> - allocating memory in advance without knowning how much will be used
> is uneconomical.
>
> But API doesnt state the memory should actually be alocated.
> It can be interpreted as a maximum to allocate if needed
> size, wich is better than infinite, in the sense you can tell it to be
> comfortable big (in terms of HTML docs e.g. 1MByte), without
> forcing servlet engine to actually alocating, only to treat the overriding
> this limit as an implicit commit to the response.
That is a completely fair point :) I still feel uncomfortable with trying to
predict how much output I'm going to produce.
> I see such a limit more as a way to deal with some errors, like
> an infinite loop writing html.
Although the container won't detect that error, since when the buffer is full it
will start sending to the client (who will presumably kill it at some point).
Actually, that scenario is probably preferable.
Regards,
jon
--
Jon Saville
Principle Member of Technical Staff - IP Telephony Program Manager
# The opinions expressed in this message are my own and do not
# represent the opinions of others or Signals & Software company policy.
Signals+Software Ltd Tel: +44 (0)20 8 872 9000
The Heights, Lowlands Road Fax: +44 (0)20 8 872 9001
Harrow, Middx, HA1 3AW, UK Web: www.sasl.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
