- From: Joseph Kesselman <keshlam@us.ibm.com>
- Date: Thu, 28 Mar 2002 15:50:22 -0500
- To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
- Cc: "'www-dom@w3.org'" <www-dom@w3.org>
On Thursday, 03/28/2002 at 01:11 MST, "Arnold, Curt" <Curt.Arnold@hyprotech.com> wrote: > The second concern is that allowing reuse makes it unsafe to provide access > to a result set that is part of the state of an object No different from any other mutable object, right? If this is a concern for the user, s/he passes in null and obtains a new instance. If they _know_ they can safely reuse, they do so. Give them the tool, let them figure out when to use it and when not to. > This could be addressed by providing a mechanism that where the application > can mark a XPathResult as not being reusable. Frankly, that strikes me as overkill -- if you don't _know_ that it's reusable in your context you should assume it isn't, again just like any other mutable object -- but if folks really thought a safety net was necessary ... ______________________________________ Joe Kesselman / IBM Research
Received on Thursday, 28 March 2002 15:51:08 UTC