Cart
[Home] [By Thread] [By Date] [Recent Entries]
It is perfectly reasonable to want to receive an XML message containing a bunch of information about an equity. It is perfectly reasonable to want to offer an object-oriented interface to that information with methods like price(), revenue(), and expenses(). There's no reason to expect that the XML message is anything like a direct serialization of the object instance. XML buys you interoperability, and the price you have to pay is the work of loading incoming data from XML's optimized-for-generality layout to your internal software's optimized-for-your-problem layout. Fortunately, this is usually not rocket science and provides a valuable level of decoupling between your software and your network. Adam's a smart guy and genuinely gets XML at a deep level. He has successfully demonstrated that for programmers, fishing information at run-time directly out of XML messages is klunky and awkward. D'oh. What next? -Tim
|
