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

Re: SAX/Java Proposed Changes

• To: "Karl Waclawek" <karl@w...>
• Subject: Re: SAX/Java Proposed Changes
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Mon, 8 Mar 2004 11:02:16 -0500
• Cc: <sax-devel@l...>, <xml-dev@l...>
• In-reply-to: <007201c40525$00ac57c0$9e539696@citkwaclaww2k>
• References: <200403071358418.SM05492@evanslt><404B7BF3.7030606@s...> <002801c404ca$cfb86690$0207a8c0@karl><404C22B7.9020500@s...><003701c40517$237d2fd0$9e539696@citkwaclaww2k><p06010207bc72317626a7@[192.168.254.4]><006c01c4051c$db4a7690$9e539696@citkwaclaww2k><p06010208bc723aca57a1@[192.168.254.4]><007201c40525$00ac57c0$9e539696@citkwaclaww2k>

At 10:49 AM -0500 3/8/04, Karl Waclawek wrote:

>Well, obviously, any initialization or cleanup methods would have to
>be exposed, that was the point about adding a parsingDone() method.
>I guess there was a misunderstanding.

I would prefer to avoid adding methods to the API when methods 
already exist that serve this purpose, even if their names aren't 
ideal.

>If I use a Stream, then I should close it at the end.
>Does that mean the Stream class has a bad API?

No, in the stream API the behavior of each method is well-defined 
irrespective of order. If you call don't call close() at the end, 
nothing bad happens. If you call close at the beginning the 
read()/write() methods still behave as documented. No method fails to 
do its job simply because its called before or after another method. 
The larger program that uses the class may depend on a specific order 
of method invocations. However, the class itself exposes only atomic 
operations.


>The contentHandler would still do its own cleanup.
>Just not throught endDocument(), which should serve a different purpose.

I'm not sure we need two methods here.

-- 

   Elliotte Rusty Harold
   elharo@m...
   Effective XML (Addison-Wesley, 2003)
   http://www.cafeconleche.org/books/effectivexml
   http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA

• References:
  • RE: SAX/Java Proposed Changes
    • From: "Kirk Allen Evans" <kaevans@x...>
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>
  • Re: SAX/Java Proposed Changes
    • From: "Karl Waclawek" <karl@w...>
  • Re: SAX/Java Proposed Changes
    • From: Dennis Sosnoski <dms@s...>
  • Re: SAX/Java Proposed Changes
    • From: "Karl Waclawek" <karl@w...>
  • Re: SAX/Java Proposed Changes
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: SAX/Java Proposed Changes
    • From: "Karl Waclawek" <karl@w...>
  • Re: SAX/Java Proposed Changes
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: SAX/Java Proposed Changes
    • From: "Karl Waclawek" <karl@w...>

• Prev by Date: Re: SAX/Java Proposed Changes
• Next by Date: RE: W3C suckered by Microsoft?
• Previous by thread: Re: SAX/Java Proposed Changes
• Next by thread: RE: SAX/Java Proposed Changes
• Index(es):
  • Date
  • Thread