jade-develop mailing list archive: RE: [jade-develop] BlueJADE

Subject: RE: [jade-develop] BlueJADE package available
From: Bellifemine Fabio (Fabio.Bellifemine@TILAB.COM)
Date: Tue Sep 17 2002 - 19:04:55 MET DST

Dear JADE users and agent programmers,
as a follow up of the announcement of Dick Cowan, on behalf of the JADE team, I would like to open a new thread of discussion.
The usage of the jade.wrapper API allowed Dick to integrate JADE as a service of an Application Server. This is surely a valid step towards the integration with the web world but the question that we have is the following: what is the final goal that we should try to reach, i.e. what should be done after this step?

In order to get answers to this difficult question for the entire agent community, of course we should try to start from the analysis of the requirements.

1. What are the advantages that a developer of multi-agent systems, in particular a JADE programmer, gets in using JADE integrated into an Application Server (e.g. in JBoss)? Why he should decide to do that?
Maybe simply because he needs to deploy its application on a Web server. And then, how we would like to partition the tasks between the Application Server and the JADE environment?

2. The other way around. What are the advantages that a developer of Web applications gets in using JADE?
For instance, the fact that he can implement a control logic with a life cycle independent of a Web session and where independent threads can easily communicate each other. Example: a user logs into a web site, fills a form with indications about an item to sell/buy, and then he logs off; the web session terminates but a JADE agent is created with the goal of accomplishing the user task.

I would really appreciate feedback and input from the entire community.

Kind regards, Fabio.

as a follow up of the announcement of Dick Cowan, on behalf of the JADE team, I would like to open a new thread of discussion.

The usage of the jade.wrapper API allowed Dick to integrate JADE as a service of an Application Server. This is surely a valid step towards the integration with the web world but the question that we have is the following: what is the final goal that we should try to reach, i.e. what should be done after this step?

In order to get answers to this difficult question for the entire agent community, of course we should try to start from the analysis of the requirements.

1. What are the advantages that a developer of multi-agent systems, in particular a JADE programmer, gets in using JADE integrated into an Application Server (e.g. in JBoss)? Why he should decide to do that?

Maybe simply because he needs to deploy its application on a Web server. And then, how we would like to partition the tasks between the Application Server and the JADE environment?

2. The other way around. What are the advantages that a developer of Web applications gets in using JADE?

For instance, the fact that he can implement a control logic with a life cycle independent of a Web session and where independent threads can easily communicate each other. Example: a user logs into a web site, fills a form with indications about an item to sell/buy, and then he logs off; the web session terminates but a JADE agent is created with the goal of accomplishing the user task.

This archive was generated by hypermail 2a22 : Tue Sep 17 2002 - 19:05:18 MET DST