On Thu, Jan 15, 2009 at 5:05 AM, Ricardo Aráoz <[email protected]> wrote:
> I'm not getting through (probably my fault). What I mean to say
> (ask/suggest) is that as a data representation XML seems to have only 2
> advantages over some other reasonable binary format. These are that it
> is human readable and that it has been widely adopted as a standard
> (which brings with it loads of things as already built libraries in
> almost any language that can generate/read it, etc). And against it goes
> the fact that it seems to be monstrously inefficient if you consider
> size (that would be speed of transmission, storage efficiency, etc).
> I wanted to talk about these subjects and see if I was missing some
> other important points in these issues.
---------------------------------------------------------------
I disagree with your list of differences.
if (Binary = .dbf)
{
You now need multiple files instead of a single one.
After your receive the second is there any indication that the
third is required (memo file)
There is a ton of wasted space in a dbf file in char columns.
Are foxpro indexes readable from dbase4 and are dbase 4 indexes
read from VFP?
Can you pass a table read in ram to another process running on
another server, possibably get it back with changes made to it's rows?
The dbf Date has always been a problem and the concept of
Empty(myDate) is just a fox thing and not understood by other date
environments.
}
if(data == "HumanReadable")
{
Transport = "poor";
Speed = "terrible";
security="fatal";
}
I see this instead:
<?xml version="1.0"?>
<product>
<category>desserts</category>
<item>Banana Split</item>
<inventory>
<sku>Banadess3nz4Zv</sku>
<price>10.43</price>
<inventory>0</inventory>
</inventory>
<vendor>The Baking Pan</vendor>
</product>
I am receiving relevant data about what I am asking for packaged
together, instead of needing 3 tables sent for the same information.
When it is only a single row <item>Banana Split</item> this rocks. If
it was the entire offereings table where Item is home to then, having
full tables is better. But in all honesty XML revolves around the
"condensed" delivery of data and not the delivery of entire databases.
Condensed = tiny subset or concept and all it's relevant
information.
>From the dbf POV that is not how you see things, you see TABLES of
data, not collections of information.
>From the sample above I coule have created the menu for lunch at the
cafeteria today, and presented it with an XSLT to link up Entree,
Meal, Bread, Desert, Drink items easily for presentation.
That is the power of XML for just a starter.
I also see things outside of just tables of data, and that is
something to overcome when learning any newer language when your have
that foxpro background.
--
Stephen Russell
Sr. Production Systems Programmer
First Horizon Bank
Memphis TN
901.246-0159
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
