NYCPHP Meetup

[Jon Baer]

Well normally its suffice to say that if you have even > 1000 XML files that
you shouldn't even be using XML @ all ... if you need to query out an XML to
someone (say a client or web service client) then you'd build a layer
between a database and the client to format the results to XML and use the
same tool to suck in the data.

Client/XML <-> [My PHP Layer] <-> Database

Do you know if your current method is sucking up all the XML into
DOM/Memory?  This would cause the box to crawl to a halt.

- Jon

----- Original Message ----- 
From: "Larry Chuon" <LarryC at indexstock.com>
To: "NYPHP Talk" <talk at nyphp.org>
Sent: Tuesday, May 06, 2003 1:49 PM
Subject: RE: [nycphp-talk] XML files


> I'm doing everything that you mention below.  Each file associates with a
> product.  It also has an image as well.  The image will have IPTC header
> that describe the product, price, model, make and etc.  Let me know if you
> need more info.  Thanks.
>
> -----Original Message-----
> From: Jon Baer [mailto:jonbaer at jonbaer.net]
> Sent: Tuesday, May 06, 2003 4:46 PM
> To: NYPHP Talk
> Subject: Re: [nycphp-talk] XML files
>
> What are you looking to do with the files? (ie, display, query, export,
etc)
> . when in doubt, go SAX :-)
>
> - Jon
>
> ----- Original Message -----
> From: "Larry Chuon" <LarryC at indexstock.com>
> To: "NYPHP Talk" <talk at nyphp.org>
> Sent: Tuesday, May 06, 2003 1:41 PM
> Subject: [nycphp-talk] XML files
>
>
> > I have nearly a million XML files generated from the database for
products
> > in my OSSuite application.  What is the best way to handle so many tiny
> > files?  Windows crawl to its knees when I try to open up the directory
> where
> > the files locate at.  Is there a way to optimize disk I/O?
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
> --- Unsubscribe at http://nyphp.org/list/ ---
>
>
>