Examples of Agent

• agent.Agent
  @author Marco Celesti
• aima.core.agent.Agent
  Artificial Intelligence A Modern Approach (3rd Edition): Figure 2.1, page 35.
  Figure 2.1 Agents interact with environments through sensors and actuators. @author Ravi Mohan @author Ciaran O'Reilly
• ch.idsia.ai.agents.Agent
  Created by IntelliJ IDEA. User: Sergey Karakovskiy Date: Mar 28, 2009 Time: 8:46:42 PM package ch.idsia.ai.agents;
• com.adito.agent.client.Agent
  Concrete implementation of an {@link AbstractVPNClient} that runs asstandalone applicaiton launched from the Adito web interface (via the Laumcher applet.

  See package description for more information.

• com.almende.eve.agent.Agent
• com.barchart.feed.api.Agent
  General agent for users, adds include/exclude w/o Rx. Should not be used by platform.
• com.caucho.bam.actor.Agent
  A BAM Actor sends and receives messages as the core class in a service-oriented architecture.

  Core API

  Each actor has a unique address, which is the address for messages sent to the actor. addresss look like email addresses: harry@caucho.com or harry@caucho.com/browser. {@link com.caucho.bam.stream.MessageStream} is the key customizable interfacefor an agent developer. Developers will implement callbacks for each packet type the agent understands. Most developers will extend from {@link com.caucho.bam.actor.SimpleActor}instead of implementing Actor directly. SimpleActor adds an annotation-based message dispatching system to simplify Actor development.
• com.cumulocity.model.Agent
• com.day.cq.replication.Agent
• com.jacobpatterson.csci446.program1.core.agents.Agent
• com.stimulus.archiva.domain.Agent
• com.sun.enterprise.admin.monitor.callflow.Agent
  This interface exposes the call flow agent API. This is intended to be called by various container trap points. An implementation of the call flow agent would collect the data supplied, and persist it, for later querying and analysis. Further, it is possible to set filters, based on client side attributes such as caller IP address and caller security principal (USER). The trap point call sequence has a specific order: { requestStart, addRequestInfo*, requestInfoComplete, (startTime, (webMethodStart|ejbMethodStart))*, ((ejbMethodEnd|webMethodEnd), endTime)*, requestEnd } Data schema: Tables RequestStart: { RequestId, Timestamp, CallerIPAddress, RemoteUser } RequestEnd : { RequestId, Timestamp } StartTime : { RequestId, TimeStamp, ContainerTypeOrApplicationType } EndTime : { RequestId, TimeStamp, ContainerTypeOrApplicationType } MethodStart : { MethodName, RequestId, Timestamp, ComponentType, ThreadId, AppId, ModuleId, ComponentId, TransactionId, SecurityId } MethodEnd : { RequestId, Timestamp, Exception } @author Ram Jeyaraman, Harpreet Singh, Nazrul Islam, Siraj Ghaffar @date March 21, 2005
• com.sun.messaging.jmq.jmsserver.management.agent.Agent
  The Main class for the broker JMX Agent.
• cu.repsystestbed.entities.Agent
• cz.cuni.mff.abacs.burglar.logics.objects.agents.Agent
  Interface of the moving elements of the game. Can be guards, burglars, dogs... @author abacs
• de.tuclausthal.informatik.winf.mobileagents.agent.Agent
  The interface Agent provides the methods a mobile agent in this framework has to provide in order to be executed, transfered and managed by a utilizing application. An agent can be described as a state machine which implementation is in start();. Agents may send and receive messages to communicate with other agents and/or hosts. An agent has a reference to its execution environment, a so called container, which it may use to initiate actions, e.g. send a message or require the de.uniol.informatik.vlba.purplebee.transfer to another host. The agent does only interact with the container but not with any other component in the application or the network. @author dluebke @version 1.0.3 (2003-11-26) @see de.tuclausthal.informatik.winf.mobileagents.container.Container @since 1.0
• edu.harvard.hul.ois.jhove.Agent
• edu.harvard.hul.ois.mets.Agent
• edu.indiana.dlib.metsnav.mets.v1_4.Agent
  agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. @version $Revision: 78 $ $Date: 2008-01-09 14:32:36 -0600 (Wed, 09 Jan 2008) $
• edu.indiana.dlib.metsnav.mets.v1_5.Agent
  agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. @version $Revision: 78 $ $Date: 2008-01-09 14:32:36 -0600 (Wed, 09 Jan 2008) $
• edu.indiana.dlib.metsnav.mets.v1_6.Agent
  agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. @version $Revision$ $Date$
• edu.neu.ccs.task.agent.Agent
  A very simple dialogue agent designed for system-directed dialogue with multiple choice input.

  The agent tracks its intentional state using a plan tree, and maintains dialogue state by keeping track of a focus within that tree. At each turn, it tries to find an elaboration that adds to the plan tree as near the focus as possible, and has a primitive task as a leaf. It then adds this to the tree and executes the task (which becomes the new focus).

  This class provides no UI; see {@link AgentConsole} and {@link AgentServer}, which both build (different) UIs on top of it. @author Dan Schulman @version $Id: Agent.java 1009 2011-01-21 21:02:36Z schulman $

• eu.planets_project.services.datatypes.Agent
  Planets agent representation.

  Instances of this class are immutable and so can be shared freely.

  @author Andy Jackson
• fr.irit.halterego.rrl_ggp.base.RRLAlgorithm.Agent
• groovyx.gpars.agent.Agent
  A special-purpose thread-safe non-blocking reference implementation inspired by Agents in Clojure. Agents safe-guard mutable values by allowing only a single agent-managed thread to make modifications to them. The mutable values are not directly accessible from outside, but instead requests have to be sent to the agent and the agent guarantees to process the requests sequentially on behalf of the callers. Agents guarantee sequential execution of all requests and so consistency of the values. An agent wraps a reference to mutable state, held inside a single field, and accepts code (closures / commands) as messages, which can be sent to the Agent just like to any other actor using the '<<' operator or any of the send() methods. After reception of a closure / command, the closure is invoked against the internal mutable field. The closure is guaranteed to be run without intervention from other threads and so may freely alter the internal state of the Agent held in the internal data field. The return value of the submitted closure is sent in reply to the sender of the closure. If the message sent to an agent is not a closure, it is considered to be a new value for the internal reference field. The internal reference can also be changed using the updateValue() method from within the received closures. The 'val' property of an agent will safely return the current value of the Agent, while the valAsync() method will do the same without blocking the caller. The 'instantVal' property will retrieve the current value of the Agent without having to wait in the queue of tasks. The initial internal value can be passed to the constructor. The two-parameter constructor allows to alter the way the internal value is returned from val/valAsync. By default the original reference is returned, but in many scenarios a copy or a clone might be more appropriate. @author Vaclav PechDate: Jul 2, 2009
• jade.core.Agent
  The Agent class is the common superclass for user defined software agents. It provides methods to perform basic agent tasks, such as:

  • Message passing using ACLMessage objects, both unicast and multicast with optional pattern matching.
  • Complete Agent Platform life cycle support, including starting, suspending and killing an agent.
  • Scheduling and execution of multiple concurrent activities.

  Application programmers must write their own agents as Agent subclasses, adding specific behaviours as needed and exploiting Agent class capabilities. @author Giovanni Rimassa - Universita' di Parma @author Giovanni Caire - TILAB @version $Date: 2011-06-06 09:17:37 +0200(lun, 06 giu 2011) $ $Revision: 6414 $
• jason.asSemantics.Agent
• net.fortytwo.twitlogic.persistence.beans.Agent
  two.net).
• net.lenkaspace.creeperDemo.model.Agent
  An agent accelerates randomly and notes that acceleration into a report. @author Lenka contact@lenkaspace.net @version 2.0
• org.apache.log4j.jmx.Agent
• org.apache.myfaces.trinidad.context.Agent
  The Agent interface describes the client that is making the request that will display the rendered output.

  Implementations that provide the set of capabilities must clearly define the names of these capabilities and their values.

  Capability names that are implementation private must be defined so using appropriate naming schemes. Trinidad private capability names are prefixed using "-adfinternal-xxx", and such capability names (and their values) may change at anytime (and not guaranteed to be supported in future releases).

• org.apache.qpid.qmf2.agent.Agent
  s.apache.org/jira/browse/QPID-3302>QPID-3302 has been raised. This is fixed in Qpid 0.12. @author Fraser Adams
• org.apache.qpid.qmf2.console.Agent
  Local representation (proxy) of a remote Agent.

  This class holds some state that relates to the Agent and in addition some methods may be called on the agent. destroy(), invokeMethod() and refresh() are actually called by a proxy class AgentProxy. AgentProxy is actually an interface that is implemented by Console (as that's where all the JMS stuff is), we use this approach to avoid introducing a circular dependency between Agent and Console.

  The Console application maintains a list of all known remote Agents. Each Agent is represented by an instance of the Agent class:

  The following diagram illustrates the interactions between the Console, AgentProxy and the client side Agent representation.

  @author Fraser Adams

• org.apache.ws.resource.discovery.xml.AgentDocument.Agent
• org.exist.management.Agent
  Interface to allow the JMX classes to be plugged in on systems which support it. A dummy implementation will be used if JMX is not available.
• org.gedcomx.agent.Agent
• org.ice4j.ice.Agent
• org.jfrog.build.api.Agent
  Information about the agent that triggered the build (e.g. Hudson, TeamCity etc.). @author Noam Y. Tenne
• org.jivesoftware.xmpp.workgroup.Agent
  Workgroup agents, which are stored in the database. @author Derek DeMoro
• org.mule.api.agent.Agent
  Agent is a server plugin that can be initialised, started and destroyed along with the MuleContext itself. Agents can initialise or bind to external services such as a Jmx server.
• org.nlogo.agent.Agent
• org.nlogo.api.Agent
• org.rhq.core.domain.resource.Agent
  A JON agent.
• org.simpleframework.transport.trace.Agent
  The Agent object represents a tracing agent used to monitor events on a connection. Its primary responsibilities are to create Trace objects that are attached to a specific socket channel. When any event occurs on that channel the trace is notified and can forward the details on to the agent for analysis.

  An agent implementation must make sure that it does not affect the performance of the server. If there are delays creating a trace or within the trace itself it will have an impact on performance. @author Niall Gallagher @see org.simpleframework.transport.trace.Trace

• org.springframework.hateoas.client.Agent
• org.timerescue.element.agent.Agent
  @author chamanxTODO Put it back to abstract and send the non player logic to a new agent
• org.wso2.carbon.databridge.agent.thrift.Agent
• urban.kappa.Agent
  A representation of the model object 'Agent'.

  The following features are supported:

  • {@link urban.kappa.Agent#getId Id}
  • {@link urban.kappa.Agent#getSites Sites}

  @see urban.kappa.KappaPackage#getAgent() @model @generated
• urban.model.Agent
  For example P(f~0,x) Often used in a collection to represent one side of a rule, or a shape.
• urban.urban.Agent
  A representation of the model object 'Agent'.

  The following features are supported:

  • {@link urban.urban.Agent#getId Id}
  • {@link urban.urban.Agent#getSites Sites}

  @see urban.urban.UrbanPackage#getAgent() @model @generated

Examples of urban.kappa.Agent

Examples of urban.model.Agent

Examples of urban.urban.Agent