[Aglets-developer] Profiles for the ADK Proposal

[Suhail M. A. <su...@pl...>]

Hi,

I have been poking around the ADK 2.0b for about a month now. I would =
like to get some input on some ideas I have formed lurking around in the =
user list.
It does seem that a lot of people are having problems with security. I =
think that security is quite important to running aglets in a production =
environment however most of the users that download the aglets do it =
mostly I feel for educational and learning purposes. They are mostly =
interested in the mobility aspects of agents rather than running aglets =
in a secure environment. If this reasoning is correct, I would be =
beneficial to redesign the ADK architecture to have a "pluggable" =
security architecture, i.e. have two versions of the ADK, one with =
security related components and one without.. Taking this argument =
further it would be quite helpful the ADK into the following stack:

          [ADK GUI]   intuitive interactive interface [Optional]
          [ADK CORE] consists of the absolute essential classes required =
to run aglets [Mandatory]
          [SECURE ADK] consists of the security classes required to run =
aglets securely [Optional]
          [ATP] consists of the ATP implementation [Mandatory]
          [RMI][SOAP].... the underlying protocol, RMI being default, =
others could be developed to provide a pluggable protocol support for =
ATP.

To this end I have started annotating the class diagrams for the ADK, =
its tedious work .. but I felt it would be best to get feedback from the =
ADK developer community before I get deeper into the hoopla.

Cheers
Suhail