Re: JSON

John,
I'll try to explain this and hopefully give you an answer :) Let me say
first, thanks for listening and trying to offer suggestions it is
appreciated.

Some of our customers will send us load information, EDI is one current
method, on available loads that are currently not assigned to a carrier.
Each line of data (based on the existing PF record length) could be
approximately 12k and our systems are designed to handle up to 99 lines of
data.

So they are sending us the iformation saying ok guys we have freight that
is going from point A (including multiple pickups) to point B (including
multiple destinations) and here is what we are willing to pay for you to
haul this freight. We in turn bring the data in, evaluate it and send
back a response that yes we accept it as is, reject it, or send it back
with a new proposed rate.

If I do this as XML or possibly JSON, I'm probably looking at around 240K
of data each time this is done.

Does this make a bit more sense?

Dutch