[
Lists Home |
Date Index |
Thread Index
]
The more I read the question, the less I understand. Lets read the
question again:
"Which one would be the best approach for storing the rate updates ?"
I underline the word "storing". Storing means "what can you do so that the input XML is quickly entered in the database ?". It is clear that if the XML format that is received is not in the same format as the one saved in the DB then some transformations must take place. But I do not see how the concept of "static transformations" can be applied in this case.
To me the concept of "static transformations" only has a meaning when XML and a web server is involved. If the XML data is converted to HTML which is later server to the clients then a static transformatin takes place. If the XML data is converted to HTML on request then a just in time transformation takes place. Is there more to "static transformations" than I understand ?
Regards,
Razvan
Michael Kay wrote:
>I would interpret "static transformation" here as meaning "eager
>transformation", i.e doing the transformation as soon as new information
>arrives. And that's possibly a sensible strategy, though there is far too
>little information to say this definitively. For example, if prices are
>being updated 1000 times per second and the information is only needed once
>per hour, then it would be crazy.
>
>You have to accept with a simplistic quiz like this that the more you know,
>the more you will be aware that the right answer might not be right after
>all. If you ask a maths professor what the sum of the angles of a triangle
>is, they will ask you whether the space you are in has positive or negative
>curvature...
>
>Michael Kay
>http://www.saxonica.com/
>
>
>
>
>>-----Original Message-----
>>From: Razvan MIHAIU [mailto:mihaiu@mihaiu.name]
>>Sent: 27 March 2005 05:50
>>To: xml-dev@lists.xml.org
>>Subject: [xml-dev] Quiz: static transformation vs. JIT generation
>>
>>
>>
>>Hi,
>>
>>
>>
>>
>>
>> On an XML quiz I met the following question:
>>
>>= = =
>>
>>A company wants to build a Website for trading shares. They have the
>>latest updates coming to them from various exchanges in XML
>>format and
>>they need to be able to supply the updates to the client on various
>>platforms: web + mobile + handheld devices. A processing application
>>would analyze the incoming documents and update the central database.
>>Since this is a real-time process the performance is a
>>critical requirement.
>>
>>Which one would be the best approach for storing the rate updates ?
>>
>>A. separate xml documents for each share
>>B. a single document for each share
>>C. static transformations for generating the output XML documents
>>D. just in time transformation of output XML documents
>>
>>
>>= = =
>>
>>My answer: B
>>The correct answer: C
>>
>>
>>
>> To my understanding 'static transformations' means to
>>generate HTML
>>pages from an XML source and to feed those pages to all the clients.
>>'Just in time transformations' means to transform the XML to HTML for
>>each client that requests the data.
>>
>> Is it practical to apply 'static transformations' to some
>>data that
>>needs to be processed "real-time" ? If yes, how often would you apply
>>the 'static transformation' ? If the data changes every
>>second you will
>>have to apply the 'static transformations' every second !
>>
>> Is there another way to interpret this question ?
>>
>>
>>
>>Regards,
>>Razvan
>>
>>
>>
>>www.mihaiu.name
>>
>>
>>
>>-----------------------------------------------------------------
>>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>>initiative of OASIS <http://www.oasis-open.org>
>>
>>The list archives are at http://lists.xml.org/archives/xml-dev/
>>
>>To subscribe or unsubscribe from this list use the subscription
>>manager: <http://www.oasis-open.org/mlmanage/index.php>
>>
>>
>>
>>
>
>
>
>
>
>
>
|
