Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Home » Archived » Test and Performance Tools Platform (TPTP) » Agents and plugins semantic

Agents and plugins semantic [message #76092]

Mon, 03 July 2006 04:37

Eclipse User

Originally posted by: RGuschin.computel.ru

Agent Controller has agents and has plugins. What are their difference
and purpose of such architecture?

Re: Agents and plugins semantic [message #76131 is a reply to message #76092]

Mon, 03 July 2006 13:15

Eclipse User

Rodion Guschin wrote:
> Agent Controller has agents and has plugins. What are their difference
> and purpose of such architecture?

The "plugins" are really a misnomer. It's a hold-out from the RAC days
where they perpetuated the NAME plugins from Eclipse for a slightly
different idea. The AC from the start wanted to deal with "agents", and
thus the agents directory has entries for all the agents it should know
about, and each agent has an agent.xml file configuring it.

When 4.2 was coming along and it became clear that we couldn't just
"switch" from the RAC to the AC, but instead had to provide backward
compatibility (BC) in the AC so as to run legacy agents, we had to keep
this nomenclature.

So, in general, agents that are new and wish to deal with the "new tech
AC" and its API only should probably go the agent route. Existing agents
will (hopefully) migrate from the plugins area to the agents directory.

Sorry for the confusion... it confused all of us as well as we got into
TPTP.

--
RDS

Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)

Re: Agents and plugins semantic [message #76178 is a reply to message #76131]

Tue, 04 July 2006 03:23

Eclipse User

Originally posted by: RGuschin.computel.ru

Thanks :)

Randy D. Smith wrote:
> Rodion Guschin wrote:
>> Agent Controller has agents and has plugins. What are their difference
>> and purpose of such architecture?
>
> The "plugins" are really a misnomer. It's a hold-out from the RAC days
> where they perpetuated the NAME plugins from Eclipse for a slightly
> different idea. The AC from the start wanted to deal with "agents", and
> thus the agents directory has entries for all the agents it should know
> about, and each agent has an agent.xml file configuring it.
>
> When 4.2 was coming along and it became clear that we couldn't just
> "switch" from the RAC to the AC, but instead had to provide backward
> compatibility (BC) in the AC so as to run legacy agents, we had to keep
> this nomenclature.
>
> So, in general, agents that are new and wish to deal with the "new tech
> AC" and its API only should probably go the agent route. Existing agents
> will (hopefully) migrate from the plugins area to the agents directory.
>
>
> Sorry for the confusion... it confused all of us as well as we got into
> TPTP.
>

Previous Topic:	Don't see any agents when trying to attach remote java procees
Next Topic:	Automated GUI Recording and Swing/AWT

Goto Forum:

-=] Back to Top [=-

Current Time: Thu May 01 05:18:09 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter