[
Lists Home |
Date Index |
Thread Index
]
M.A.,
Besides the possibility of compression, one approach is to simply cut
down the file sizes. For example, suppose an XML file is sent from a
U.S. state to the federal government, and it contains environmental
reporting information. A given state may want to send a file containing
all counties and cities. Perhaps an XML file containing state-wide
information is too large - so the submitters may be asked to "segment"
the data into separate files for each county, or each city, etc.
I realize that this is an example where information is being reported in
an organized way (i.e. "for each county", "for each city within county
X", etc.) so it's more straightforward in that the queries/file output
can be adjusted accordingly. Your situation may not allow this level of
flexibility, however. Also, sometimes pushing this "burden" back to the
submitters meets with resistance.
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
> "Miguel A. Robles" wrote:
>
> Dear colleagues,
>
> I usually work with XML for sending on information between different
> servers or applications. For example, currently I'm working with web
> services and everithing works fine. The problem appears now, because I
> have to parse a document containing a lot of information. DOM is not
> enough to accomplish the object because the document
> is extremly large, and I don't know how SAX deals with this kind of
> files.
>
> I know that XML is not intended for containing so much information,
> but I have to think about a possible solution.
>
> What do you think I could act to fix the problem?
>
> Thanks a lot.
>
> Regards,
> M. A.
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
- References:
- Big XML file
- From: "Miguel A. Robles" <marobles.sag@mail.sgae.es>
|
