Difference between revisions of "On Demand"

From PresenceWiki
Jump to: navigation, search
(On Demand)
(On Demand)
Line 5: Line 5:
 
This is performed through the following mechanism:
 
This is performed through the following mechanism:
  
- [[On Demand Client]] makes a call to the Presence [[Work Server]]. This is typically embedded within a Web application server such as Tomcat, Glassfish or Resin.
+
- [[On Demand Client]] makes a call to the [[Presence Server]].  
  
- [[Work Server]] executes the Task, identified by its alias
+
- [[Presence Server]] executes the Task, identified by its alias, see [[Live Task Queue]] for information on defining On Demand tasks aliases.
  
 
- Response is sent back to the [[On Demand Client]]
 
- Response is sent back to the [[On Demand Client]]
  
 
See also: [[Calling On Demand Tasks]]
 
See also: [[Calling On Demand Tasks]]

Revision as of 09:07, 20 August 2015

On Demand

As well as being set to run at certain times, Presence also allows Tasks to be accessed "On Demand" from a web server or application. This gives you the powerful option of using Presence to generate dynamic web content.

This is performed through the following mechanism:

- On Demand Client makes a call to the Presence Server.

- Presence Server executes the Task, identified by its alias, see Live Task Queue for information on defining On Demand tasks aliases.

- Response is sent back to the On Demand Client

See also: Calling On Demand Tasks