创建一个简单的移动代理系统
我希望创建一个简单的移动代理系统，它将处理 4 个任务，即 4 个不同的移动代理作业：数据库更新、会议安排、网络服务发现和内核更新。
我做了研究，看到了不同的框架，如 Aglet、Jade、代理构建器等。我的问题是我应该使用哪一个？另外，我需要设置基本代码才能正常工作，有人可以向我指出一个站点或帮助我设置移动代理的基本功能吗？
我读过有关 Aglet 模型的塔希提岛服务器的信息。我对如何设置移动代理系统感到很困惑。任何帮助将不胜感激。
我也尝试过使用 RMI 来实现。我创建了一个类型代理的方法，但无法通过远程方法实现传递它。我正在阅读有关 tcp 和 udp 套接字编程的内容。我在想使用套接字编程可能会更公平。这样的话，这还叫代理吗？我正在考虑服务器向多个客户端发送数据报包。
I am looking to create a simple mobile agent system which will deal with 4 tasks, i.e 4 different mobile agents jobs: Database update, meeting scheduling, network services discovery and kernel update.
I have done my research and have seen different frameworks such as Aglet, Jade, agent builder etc. My question is which one should i use? Also i need to setup the base code for it to work, can someone point me to a site or help me to setup the basic functions of the mobile agent?
I've read about tahiti server for the Aglet model. I'm quite confused about how to set up the mobile agent system. Any help would be much appreciated.
I have also tried to it using RMI. I had created a method of type agent, but i couldn't pass it through remote method implementation. I was reading about tcp and udp socket programming. I was thinking may be it would be more fair to do it using socket programming. In this case, would this be called an agent? I was thinking about the server sending datagram packets to multiple clients.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您需要问自己为什么要使用移动代理。移动代理的概念在 90 年代初在代理研究社区中很流行，但后来失宠了，因为 (i) 不清楚它要解决什么问题，(ii) 允许任意代码迁移到一台特定的计算机并具有足够的权限来访问本地数据和服务，这很容易被滥用，并且（iii）移动代理的所有声称的好处实际上都可以通过 Web 服务（REST 或其他）和开放数据格式来实现，例如RDF。因此，自早期实验以来，很少有移动代理平台得到妥善维护。
听起来您似乎还需要明确要解决哪个最终用户问题。安排会议和更新内核是非常不同的任务 - 对于一个声称可以同时完成这两项任务的程序，我会感到非常不舒服。如果您对大型网络上的系统维护任务（例如数据库调整和内核修补）的自动化感兴趣，您可能需要查看SmartFrog 项目，或阅读自主计算< /a>.
You need to ask yourself why you want to use mobile agents at all. The notion of a mobile agent was popular in the agent research community in the early 90's, but fell out of favour because (i) it wasn't clear what problem it was solving, (ii) the capability to allow arbitrary code to migrate to a particular computer and execute with enough privileges to access local data and services is very open to abuse, and (iii) all of the claimed benefits of mobile agents can actually be achieved though web services (REST or otherwise) and open data formats such as RDF. Consequently, few, if any, mobile agent platforms have been properly maintained since the early experiments.
It also sounds as though you need to be clear which end-user problem you want to solve. Scheduling a meeting and updating my kernel are very different tasks - I'd be very uncomfortable with a program that claims do both. If your interest is in the automation of system maintenance tasks, such as DB tuning and kernel patching, on large networks you might want to look at the SmartFrog project, or read up on autonomic computing.
我使用 JADE，我同意第一个人的观点，代理系统通常需要大量开销，所以如果你能避免它，请这样做。但是，如果您选择继续，请选择一个拥有大量支持和庞大用户群的平台。
Jade 有一些巧妙的功能，例如目录服务程序 DF，其工作方式类似于黄页，因此其他代理不必知道正在运行哪些代理以及提供哪些服务，他们只需通过 DF 进行查询即可。
JADE ContractNetBehaviours 还有助于简化沟通。
I use JADE and I agree with the first guy, agent systems usually take alot of overhead to going so if you can avoid it, please do. If however you choose to proceed choose a platform with alot of support and a big user group.
Jade has some neat features like a directory facilitator DF, which works like a yellow pages so other agents don't have to know what agents are running and what services are supplied they can simply inquire by the DF.
Also JADE ContractNetBehaviours help simplify communication.