Dear authors,
Your work is quite excellent, and here are some suggestions I have. 1. The ALTO server should have the capability to track and record the most frequently used or requested cost metrics of each ALTO client. I’m not sure if it is true, that each client may only run one or two certain applications at most of the time. Then, the benefit is that the ALTO server can prepare the cost metrics in advanced and respond the clients fast after receiving the request. 2. Another benefit of recording the type of cost metrics of each client is that the ALTO server can detect abnormal behavior of client or application, such as database resource leaks, illegal occupation, or other security issues. 3. A variety of performance cost metrics also raise an interesting scheduling problem. For example, client “A” requests two metrics, client “B” just requests one, and client “C” requests three metrics, then how the ALTO server schedules to respond them in the constraint of given resources for workload processing and network transmitting. And for each client, what is the order of the cost metric types to be returned? Hope these are helpful. Best, Geng Computer Science, Yale
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
