Hi Andy,

I'll take that as a +0.  I do agree that this feels a bit kludgy, but I
guess the point is that it will often make sense to modify the pipeline
dynamically based on what's seen, and the only really obvious place where
knowledge of how to do this could live is in a component which is watching
events go by.

So I'll get the relevant changes ready, but I've now got some other more
pressing work to do, so it might be a little while before this appears in
CVS...  Stay tuned!

Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  [EMAIL PROTECTED]




|---------+---------------------------->
|         |           Andy Clark       |
|         |           <[EMAIL PROTECTED]|
|         |           >                |
|         |                            |
|         |           11/21/2002 09:21 |
|         |           PM               |
|         |           Please respond to|
|         |           xerces-j-dev     |
|         |                            |
|---------+---------------------------->
  
>---------------------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                                                         |
  |       To:       [EMAIL PROTECTED]                                        
                                                         |
  |       cc:                                                                          
                                                         |
  |       Subject:  Re: [PROPOSAL]:  minor XNI change                                  
                                                         |
  |                                                                                    
                                                         |
  |                                                                                    
                                                         |
  
>---------------------------------------------------------------------------------------------------------------------------------------------|



[EMAIL PROTECTED] wrote:

> Now, if I get your proposal correctly, the filter has to do a check to
see
> whether it has an XMLDocumentHandler on one end, or an XMLDocumentFilter.
> If the latter, it needs to set its source on it; otherwise, it can't.


Yeah, you're right there. Annoying. I thought I was
on to something for a second. Oh well...

I *still* don't like letting components muck around
with the pipeline. We could do it without having
these methods but we would need some *other*
mechanism to tell the parser configuration to
re-arrange the pipeline. Ugh. I guess I have to
live with the methods.
--
Andy Clark * [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to