14 Jun
2014
14 Jun
'14
11:27 p.m.
Hi,
I would distinguish between use cases.
XMLDOM is extremely convenient for prototyping in particular in conjunction
with GTInspector. I do not have to leave the inspection context to write
code somewhere else and come back at a later time. Instead I focus on
extracting what I want. I worked like this with XML files of ~100MB without
any problems other than the funny default size limit that you have to
overpass explicitly.
However, it is true that I would not recommend it for long term usage.
Cheers,
Doru
On Sat, Jun 14, 2014 at 11:00 PM, Hernán Morales Durand <
hernan.morales(a)gmail.com> wrote:
I am *very* suprised of this thread given that I have
reported several
times in the pharo mailing lists that XML DOM parsing is not the right
solution for processing large XML files.
XMLDOM parsing is not even adequate for files larger than 10 Mbytes.
Why some people insist using it?
The XMLPullParser is the right way to go.
Cheers,
Hernán
2014-06-11 12:01 GMT-03:00 Serge Stinckwich <serge.stinckwich(a)gmail.com>om>:
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
hum, you are right, I have to think how to reduce
the footprint of my
model creation ...
I don't have time to wait for Spur ;-)
On Wed, Jun 11, 2014 at 4:53 PM, Tudor Girba <tudor(a)tudorgirba.com>
wrote:
> I see. But, I think your problem is of a
different nature given that you
> said that it went to 1.9 Gb :)
>
> Doru
>
>
>
>
> On Wed, Jun 11, 2014 at 4:38 PM, Serge Stinckwich
> <serge.stinckwich(a)gmail.com> wrote:
>>
>>
>>
>>
>> On Wed, Jun 11, 2014 at 4:22 PM, Tudor Girba <tudor(a)tudorgirba.com>
wrote:
>>>
>>> I am not sure I understand.
>>>
>>> The issue is not the XML loading at all. Instead, it seems to be in
the
> code that produces the model out of the DOM tree.
Yes, you are right.
>
> In this case, why would you look for the PullXMLParser?
>
Saving some memory space for my model ;-)
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev