You are here: Recent News » Projects » ActionStep » ActionStep Features » RPC

 

RPC

The ActionStep framework contains a Remote Procedure Call (RPC) package, made up of both abstract and concrete classes.

Currently there are the following implementations of the above package:

Package Listing

ANS Remoting Classes MM Remoting Classes
org.actionstep.ASDebugger mx.services.Log
org.actionstep.rpc.remoting.ASRemotingService mx.data.components.RemotingConnector
org.actionstep.rpc.remoting.ASFault mx.rpc.Fault
org.actionstep.rpc.remoting.ASFault mx.rpc.FaultEvent
org.actionstep.rpc.ASRelayResponder mx.rpc.RelayResponder
org.actionstep.rpc.ASResponderProtocol mx.rpc.Responder
– none – mx.rpc.ResultEvent
– none – mx.remoting.debug.NetDebug
– none – mx.remoting.debug.NetDebugConfig
org.actionstep.ASConnection mx.remoting.Connection
see Binding mx.remoting.DataGlue
– deprecated – mx.remoting.NetServices
org.actionstep.rpc.remoting.ASRemotingPendingCall mx.remoting.PendingCall
org.actionstep.rpc.remoting.ASRecordSet mx.remoting.RecordSet
org.actionstep.rpc.remoting.ASRemotingService mx.remoting.Service

projects/actionstep/documentation/rpc.txt · Last modified: 2007/02/19 11:20 by niko