Re: XFastParser - next steps ...

2016-08-01 Thread Michael Meeks
Hi Mohammed, On Mon, 2016-08-01 at 12:09 +0530, Mohammed Abdul Azeem wrote: > A. optimize clearing the pending events - unlikely to > give >a big win, but nice. > > This is done. Great. > B. merge the legacyfastparser pieces in

Re: XFastParser - next steps ...

2016-07-28 Thread Michael Meeks
Hi Mohammed, Summarizing where we're at: No. Of Records in ods sax_expat #1 #2 1 million 8s 20.5s 11s 50 million23.4s 26.3s 22s #1 - first cut of XParser implemented on FastParser #2 - second cut avoiding bogus tokenizer calls ... >

Re: XFastParser - next steps ...

2016-06-28 Thread Michael Meeks
Hi Michael, Thanks for your mail. On Tue, 2016-06-28 at 20:53 +0200, Michael Stahl wrote: > > Then (I guess) we could pass namespace prefixed names through for the > > unknown attributes so eg. "office:foo" - and still have the information > > we need to properly resolve them. > > uh

Re: XFastParser - next steps ...

2016-06-28 Thread Michael Stahl
On 28.06.2016 18:28, Michael Meeks wrote: > Hi Mohammed, > > Let me CC the dev list on the fag-end of this conversation; hopefully > it will get more interesting over time =) > > On Mon, 2016-06-27 at 22:01 +0530, Mohammed Abdul Azeem wrote: >> I'm looking into the code paths which misuses

Re: XFastParser - next steps ...

2016-06-28 Thread Michael Meeks
Hi Mohammed, Let me CC the dev list on the fag-end of this conversation; hopefully it will get more interesting over time =) On Mon, 2016-06-27 at 22:01 +0530, Mohammed Abdul Azeem wrote: > I'm looking into the code paths which misuses defined namespaces > without resolving them. I will m