Hi, In part II, the java application client for agent is confusing. I don't see the reason that they are not just using web. If we use an application, we will have a different set of UserInterfaces and also some additional controller classes. I.e. we will have a HTTP proxy to simulate the HTTP requests and receive HTTP results and let the java client render the HTTP results. It is kind of complicated. Do we need to put the java client in so much details? Anybody has any comments? TIA, John.
posted 15 years ago
I have the same concern. The java application client should also have different use case action as the web user. For example, should not we put a search employee action at the beginning of prepare for itinerary use case? I just don't know if we should address this in details or not.
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads