Are mobile agents an appropriate implementation mechanism for Distributed system?

[FaisalBahadur]

Mobile agents are self Autonomous: i.e. Agent itself decides when and where to migrate next. Applying this definition to a distributed shared memory systems where client's requests are cpu-intensive tasks, can we prefer mobile agents that can select a node itself to migrate to that node and execute client request on it. Is this a good paradigm for java based distributed application where client's requests are cpu-bounded and we let the mobile agent to choose a proper node itself.? if not then what alternatives are their in this scenario?

[KevinWorkman]

Huh?

[FaisalBahadur]

plz dont reply if u dont know the answer.

[GregBrannon]

I don't think anyone understands the question, at least not in a Java context. What's a mobile agent? How does a mobile agent make decisions? What (physically or virtually) is migrating? What is a node?

The context of your question is not clear, and I suspect you're attempting to apply the constraints and mitigations of a language that requires the programmer to manage memory/CPU resources (like C) to Java which may not be appropriate.

[FaisalBahadur]

ok dear! i will talk 2 u later as i have 2 leave for university1 Bye

[aliraza8]

Mobile agents are self Autonomous: i.e. Agent itself decides when and where to migrate next. Applying this definition to a distributed shared memory systems where client's requests are cpu-intensive tasks, can we prefer mobile agents that can select a node itself to migrate to that node and execute client request





_______
razaali88

[BobS0327]

Mobile agents are self Autonomous: i.e. Agent itself decides when and where to migrate next. Applying this definition to a distributed shared memory systems where client's requests are cpu-intensive tasks, can we prefer mobile agents that can select a node itself to migrate to that node and execute client request

Translation...
Mobile agents are programs that can move thru a network under their own control, migrating from host to host and interacting with other agents and resources on each host. After the mobile agent completes it's work, it would normally return to the host of its origination.


Isn't a mobile agent itself a form of distributed computing. For example, an agent can be used by a physician on his laptop. The agent would interact with imaging department to provide xrays etc, interact with patients database to get patients medical info and also interact with the billing department to bill the patient.

Is Java a good platform for mobile agents? IMHO, yes, primarily because of platform independence. The byte code can be executed on any platform as opposed to native code. Also, there are other compelling reasons for using the Java platform. But I don't want to turn this into a long winded explanation.

can we prefer mobile agents that can select a node itself to migrate to that node and execute client request

Well, isn't this what a mobile agent is supposed to do? I'm not aware of any type of variation.