From 507411c77717e809995361ba43b1629ca567599c Mon Sep 17 00:00:00 2001 From: Editor Lionbridge Date: Fri, 28 Apr 2017 11:18:57 +0300 Subject: [PATCH] [Push] Remove guide for request by email This is a manual cherry-pick from changes #120536 and #126460 in the tizen_3.0 branch. Change-Id: I263cfebe3a8e903ae4f8bfb2c22b6f84a3c79467 --- org.tizen.guides/html/native/messaging/push_n.htm | 3 +- org.tizen.guides/html/web/messaging/push_w.htm | 96 +++++------------------ 2 files changed, 21 insertions(+), 78 deletions(-) diff --git a/org.tizen.guides/html/native/messaging/push_n.htm b/org.tizen.guides/html/native/messaging/push_n.htm index 0579b9a..f2042bf 100644 --- a/org.tizen.guides/html/native/messaging/push_n.htm +++ b/org.tizen.guides/html/native/messaging/push_n.htm @@ -58,7 +58,6 @@

Once your application is successfully registered in the push server through the push service (daemon) on the device, your application server can send push messages to the application in that particular device.

When a push message arrives when the application is running, it is automatically delivered to the application. If not, the push service makes a sound or vibrates and adds a ticker or a badge notification to notify the user. By touching this notification, the user can check the message. The application server may send a message with a LAUNCH option. In this case, the push service forcibly launches the application and hands over the message to the application as an application control.

-

To use the push messaging service, the application needs the permission to access the Tizen push server. Request the permission from the Tizen push service team by email, including the necessary information. When the team approves the request, you receive a push app ID corresponding to your package ID.

The main features of the Push API include: