Re: [REMINDER] Package Proposal: XML_SaxFilters
| From: | Harry Fuecks | Date: | Wed, 25 Jun 2003 20:48:26 +0000 |
| Subject: | Re: [REMINDER] Package Proposal: XML_SaxFilters | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17730@lists.php.net to get a copy of this message | ||
On Thu, 26 Jun 2003 00:01:38 +0400, Alexey Borzov <borz_off@cs.msu.su> wrote:
Hi! +1 for thisHi Alexy - many thanks.
I have a question, though: ExpatParser from this package covers mostly the same ground as XML_Parser already available in PEAR. Is it possible to somehow use an existing solution?Think the answer is "perhaps". There's definately some crossover and I'll give it a try and post here to see what people think. The main issue is I think I'd either have to either have to extend it or write some kind of adapter, which although nice, would probably mean a performance hit. Some of the issues include XML_Parser being specifically designed for reading from files (fopen) while I'd like to allow SaxFilters to work with a number of "streams" (in particular a string). There may be room for interesting collaboration with some of the other XML classes in particular XML_Tranformer. Got to look at this in more detail though.
Harry Fuecks wrote:OK - the first round of this proposal happened here: http://marc.theaimsgroup.com/?l=pear-dev&m=105650833122300&w=2 Please take a moment to add your + or - so I know whether to go forward with this.From the comments from the last thread, I have made / will be making thefollowing changes; - Better introductory documentation; http://code.phppatterns.com/XML_SaxFilters/docs/SaxFiltersGuide.phps - Remove includes for the interface classes (just there for the API docs) - Refactor the abstract base classes to use some kind of Abstract factory pattern like PEAR::DB. This will break the current API and is a major change (for the good) so I've dropped the version to 0.1.0 (beta)