I would basically be searching the file for a single instance of a string and grabbing the status of the url
So which would ever be fastest for searching. Which leads to your point of JSON being less verbose. I guess.. less text, faster searching. I'll look into that. On Thu, Dec 16, 2010 at 10:46 AM, Matthew Woodward <[email protected]>wrote: > On Thu, Dec 16, 2010 at 8:43 AM, Jason King <[email protected]>wrote: > >> I don't know much about it and have no experience with it. >> >> Would that be the best choice? >> > > The only valid answer without know more is "it depends." One isn't > inherently better than another, just depends on the data and how you're > going to use it. > > As a general rule, JSON tends to be less verbose than XML, plus with > SerializeJSON() and DeserializeJSON() getting JSON in and out of native CFML > datatypes is a breeze. > > But again, just depends on how you're going to use everything. > > -- > Matthew Woodward > [email protected] > http://blog.mattwoodward.com > identi.ca / Twitter: @mpwoodward > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments. > http://www.gnu.org/philosophy/no-word-attachments.html > > -- > Open BlueDragon Public Mailing List > http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon > official manual: http://www.openbluedragon.org/manual/ > Ready2Run CFML http://www.openbluedragon.org/openbdjam/ > > mailing list - http://groups.google.com/group/openbd?hl=en > -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
