Hi,

Got some comments on the 2.2 First Public Release servlet spec. Accept my
apologies if they have already been dealt with.


getRealPath
===========

Section 5.5 describes the deprecated getRealPath() method of HttpServletRequest.
This description should probably be moved to the ServletContext section.


setBufferSize
=============

Secondly, I have some disquiet about the new mechanism for buffering the
response (section 6.1). As it stands (as I understand it), a call to
setBufferSize() cannot be refused. A spec-compliant container *must* allocate a
buffer of the requested size. This is a serious matter for containers running on
systems where memory is limited.

The opening line of section 6.1 says that 'a servlet container is allowed, but
not required to by default, to buffer output going to the client.' The following
description of the API effectively adds 'but can be required to if requested by
the servlet.'

I believe the call to setBufferSize should have the ability to return the actual
buffer size allocated, which may be more *or less* than that requested. This
would allow the container to balance buffer allocation between servlets, and to
refuse outrageously large buffer requests from broken, malicious or badly coded
servlets.


Best 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
begin:vcard
n:Saville;Jon
tel;cell:+44 (0)7803 596 871
tel;fax:+44 (0)20 8872 9001
tel;work:+44 (0)20 8872 9000
x-mozilla-html:FALSE
url:www.sasl.com
org:Signals + Software Ltd;IP Telephony
version:2.1
email;internet:[EMAIL PROTECTED]
title:IP Telephony Program Manager
adr;quoted-printable:;;The Heights=0D=0ALowlands Road;Harrow;Middx;HA1 3AW;UK
fn:Jon Saville
end:vcard

Reply via email to