[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX/Java Proposed Changes

• To: <xml-dev@l...>
• Subject: Re: SAX/Java Proposed Changes
• From: "Karl Waclawek" <karl@w...>
• Date: Mon, 8 Mar 2004 00:04:18 -0500
• Cc: "Dennis Sosnoski" <dms@s...>
• References: <200403071358418.SM05492@evanslt> <404B7BF3.7030606@s...>

----- Original Message ----- 
From: "Dennis Sosnoski" <dms@s...>
To: "Kirk Allen Evans" <kaevans@x...>
Cc: <xml-dev@l...>
Sent: Sunday, March 07, 2004 2:45 PM

> As for filters and handlers, they should always initialize their state 
> on startDocument(). That will prevent any errors due to reuse after 
> attempting to parse a bad document.

I think the problem is not initialization, but rather
"finalization) - i.e. cleanup. If a filter acquired
resources, then it would not release them until (if ever)
startDocument() is called again.

Karl

• Follow-Ups:
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>

• References:
  • RE: SAX/Java Proposed Changes
    • From: "Kirk Allen Evans" <kaevans@x...>
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>

• Prev by Date: Re: [Sax-devel] Re: SAX/Java Proposed Changes
• Next by Date: Re: SAX/Java Proposed Changes
• Previous by thread: Re: OT - CSS - thoughts on non-compliant browsers
• Next by thread: Re: SAX/Java Proposed Changes
• Index(es):
  • Date
  • Thread