Conclusions

4.1 Future work

  1. A layer of security can be added by using SSL for the agent transfer
  2. More study is needed to understand the feasibility of having an agent-based system
  3. AI algorithms can be used for making mobile agents equipped with negotiation capabilities
  4. For Electronic Commerce applications, there should be a mechanism by which a agent should be able to pay for the services used.
  5. More work is needed to make the Agent Host more robust in handling various agents
  6. Agents need more error handling capabilities. In case an agent dies during a task, then the sender should be informed of the failed transaction

 

4.2 Conclusion

An agent architecture provides a flexible alternative to client/server and distributed object architectures. Java is a natural choice for implementing such a system because it is a mobile code platform with built-in support for networking. With the emergence of agent standards, we may soon see more agent systems deployed. But before an agent system is used for real-world applications, robust security mechanisms must be embedded directly into the framework. A secure agent architecture becomes a powerful solution for enterprises looking to implement scalable distributed software systems, especially over the Internet.

 

4.3 References 

1. www.agent.org
2. Have your agent call my agent , Srikanth Kannapan, Xerox Corporation, Design Research Institute
3. IBM's Aglets Home Page
4. Solve real problems with aglets, a type of mobile agent , Bill Venners in JavaWorld
5. Project: Java-To-Go, University of California at Berkeley
6. Project: Java Agents for Meta-learning (JAM) (fraud detection system), by Columbia University