The following questions concern Net-Based Report
Generation with CBD:
Would an architecture that included a message queue communication
connection be useful for this situation?
Why?
What somewhat low technology mechanism could be used to notify
a thin client when a report that takes tens of minutes to generate
is finished?
The following questions concern the Web-Based Financial
Trading System:
Why is this a client server architecture?
Is the client a fat client or a thin client?
Justify your answer.
Consider the Nirvana License and Tax System.
Could this system be implemented using a centralized architecture?
Justify your answer.
Consider the Nirvana Widget Rebate System.
Why is it probably necessary to implement this system using
a client server architecture?
Why is it not necessary to deploy the system to three tiers?
A two tier client server system is usually deployed with
one physical processor for each client and one physical processor
for the data server.
Suppose we have a system that will never have more than three
clients.
Is it possible to deploy the two tiers to a single physical
processor?
What are the requirements for such a processor?