>- see footer for list info -< hmm, that's also very useful. The app will be exporting and importing, so its 50/50 as to where the load will be, but a staged import of smaller files, phased into the various different node types would reduce the footprint considerably, as and when (and if) required, I'm sure.
Cheers guys, for a low-traffic list, cf-dev uk has a high ratio of expertise. 2009/12/6 Peter Boughton <[email protected]> > >- see footer for list info -< > Another thought to throw out there - is XML the right format for this? > > It's easy to just pick XML as convenient, but whilst it's simple, it's > not necessarily the best option. > > > Or perhaps, instead of a single monolithic XML file, perhaps you have > a number of second-level nodes that can each be written as their own > file directly into the ZIP - remember, railo has Resources, so you can > do FileWrite( "zip://c:/myzip.zip!node1.xml" , Nodes[1] ) > (can't remember exact syntax, it'll be something like that) > > If you can split the big XML into multiple ones, that means less data > in memory at any one time, because it's already written to disk, but > it would of course need stitching together again at the other end, so > it depends what you're doing whether this will work. > > _______________________________________________ > > For details on ALL mailing lists and for joining or leaving lists, go to > http://list.cfdeveloper.co.uk/mailman/listinfo > > -- > CFDeveloper Sponsors:- > >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< > >- Lists hosted by www.Gradwell.com -< > >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -< > _______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:- >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< >- Lists hosted by www.Gradwell.com -< >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
