† alert_get ( session, ticket )

To be called after a session_init () to request an end point to send notifications.

Note that alert_subscribe doesn’t require a specific format at the end point, as the result of a call to the end-point will be a alert_get () call

Input

parameters:

session:  token returned by a session_init () call

ticket: is the “whatever” reference to the alert information give it in the callback of the alert_subscription(). The tike is used by the alert subscriber service to know the user affected by the alert

Output

parameters:

message: a message in the current session language. This message may include one or more actions tagged with the <a/> tag. When the user would click any of the “tagged” words or sentence segments the client must call action_exec (session, token)

ErrorMsg: any fault in the call, either in the validation of input parameters, errors in the connection to the database or any other error, this parameter returns the error message produced

Request

sample:

alert_get ( “LCAAAAAAAAAAAA”, “123”);

Response

sample:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<message>There is a call waiting to be answered do <a hre =”toquen1”>clic</a> or <a href=”toquen2”> reject </a> </message>

<ErrorMsg></ErrorMsg>

Notes:

This function returns the same response than an action_exec () call except for the <message/> tag