Lists Home |
Date Index |
> Is there more to "static
> transformations" than I understand ?
Probably less. "static transformation" is a truly awful term for dynamic
transformations done when new information arrives. A "static
transformation" can only be interpreted as a storage technique at all if
you assume that the result of the transformation is then stored on the
website awaiting requests for it.
The trade-off this question is getting at so clumsily is between
preparing query responses in advance and preparing them on demand. The
emphasis on "real time" response stacks the deck in favor of preparing
in advance, because you can always send faster than compute and send.
However, you will sometimes be sending out stale data, because you don't
wait when a new answer is in the process of being computed. The day
trader who polls you every thirty seconds won't thank you when he gets
his ticker update 29 seconds late. The trader would be almost as well
off if you sent him email.
Incidentally, you keep trying to insert HTML into the discussion, but
there is no mention of HTML in the problem. One would assume (however
unrealistically) that query responses are being sent as XML.