ActiveSpaces Routing

The ActiveSpaces routing feature is implemented by means of a callback function, similar to the callback function used with shared-all persistence. Using routing, your application forwards updates to another site, and receives a status message in return. The operation is blocked until the status is returned.

Note: A space does not require persistence to be enabled to enable routing. If persistence is also enabled, both the persister and the router receive callbacks before completing an operation.
Related concepts
Remote Clients
The as-agent Utility as a Seeder
Special Considerations for Joining a Space or Metaspace
Networking Considerations
Deployment
Transactions
Remote Invocation of Code over a Space
Filters
Listeners
Browsers
Results
Data Lock in a Space
Concurrent Data Update in a Space
Expiration Time to Live and Tuple Locking
Space Storage Options and Persistence
Host-Aware Replication
Replication
Distribution
Space Definition
Space Members and Member Roles
The Take Operation Consuming or Removing Data from a Space
Space Data Retrieval Methods
The Put Operation Storing Data into a Space
Basic Operations on Tuples
Indexes
Tuples and Fields
Space
Metaspace
Introduction to TIBCO ActiveSpaces Applications
Performance Monitoring
The ASCommon Object
The tibasMetaspace_Connect Method
The close Method
The getSelfMember method
The getUserSpaceNames Method
File Logging
The defineSpace Method
The getSpaceDef Method
The dropSpace Method
Distribution Policy Methods
Define Capacity
Host-Aware Replication
LockTTL Methods
Methods to Define Fields
The getSpace Method
The close Method
Persistence
Tuple
The getName and getSpaceDef Methods
Context Tuples
The Read and Write in a Space
Lock and Unlock Methods
Transactions
Batch Operations
Listeners
SpaceEvent Objects
Space Browser Methods
ASEventBrowser
Performance Monitoring
Remote Space Invocation
Space as a Cache
Working with Remote Clients
Related reference
Basic ActiveSpaces Terms
Contents
Search Results