Cart
[Home] [By Thread] [By Date] [Recent Entries]
Jeff Rafter wrote: >> Any way, to pick just one drop from the ocean, if I have a large >> address book, I would expect it to be very wide, and I would probably >> want to stream to process one entry at a time. > > > Ahh, this was a very helpful example-- I totally misinterpreted what > you meant by "wide"-- though in retrospect it would have been obvious > had I considered it's opposite "deep". So I agree. I see. I was probably thinking too literally in tree terms. Colorado doesn't have many native trees that are wide, so I have to substitute *something* in my imagination, and sometimes XML does the trick :-) -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://4Suite.org http://fourthought.com Use CSS to display XML - http://www.ibm.com/developerworks/edu/x-dw-x-xmlcss-i.html Full XML Indexes with Gnosis - http://www.xml.com/pub/a/2004/12/08/py-xml.html Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286 UBL 1.0 - http://www-106.ibm.com/developerworks/xml/library/x-think28.html Use Universal Feed Parser to tame RSS - http://www.ibm.com/developerworks/xml/library/x-tipufp.html Default and error handling in XSLT lookup tables - http://www.ibm.com/developerworks/xml/library/x-tiplook.html A survey of XML standards - http://www-106.ibm.com/developerworks/xml/library/x-stand4/ The State of Python-XML in 2004 - http://www.xml.com/pub/a/2004/10/13/py-xml.html
|
