1. How can I supports both web clients and application clients and make sure the Travel Agents have the fastest system possible? Do I need monitor system speed? How can I control that? 2. As for the mileage system, I think after a successful booking, I need write something to it, but how can I do that because I can not find any interface of this mileage system.
1) I think you do not have to worry much about the speed of the system now, because which is actually achieved with clustering and load balencing.
2) The requirements clearly say that we need to interface with mileage system only to make the content available to the customer and travel agent. So we get data from it and dont update to it. When customer wants to update his mileage he will log into frequent flyer mileage system or call the frequent flyer mileage system agent to update his mileage.
Hope this clarifies
Joined: Mar 03, 2004
thanks Srinivas Your message was edited since you quoted content from the actual assignment. Please read our policy on SCEA questions and refrain from discussing actual assignment issues.
[ July 06, 2004: Message edited by: Ajith Kallambella ]
Thanks for your answers. But, I feel the following issues are not yet addressed:
1)Requirements ask for different speeds for users & agents. With clustering & other techniques, both clients can be served at a higher speed but not just GUI clients.
2)I see some serious problem if the FF system is not updated after making a reservation using the FF miles. If the system just retrieves the FF data, the next time the user checks his FF account after making a reservation using his FF mile, he will be still shown the old miles and he can make any number of reservations until someone updates the system.
Could anyone plz throw some light on these?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com