Logger Script


cloud messaging

Cloud messaging is a notification services that provide the event system.

What is messaging?

Cloud messaging is a notification services that provide the event system.

The advantage of cloud messaging service message delivery process can be simplified because it does not take into account that on the side issues a message about whether to forward the message in some way to the reception target. The use of cloud messaging services and applications they can inform themselves subject to change, a process with respect to forward the message should be received subject to any path how many turns all responsibility in the cloud messaging.

Thus, application developers and service developers and simple to implement message passing, for monitoring the state grasp between elements may also be simplified by eliminating the need to consider the message-passing process. cloud messaging service based environment that allows you to configure web-scale computing to developers through these events, the delivery system (Web-scale computing).

Service Highlights

01. Topic Creation
100 topics can be created per account.

02. Topic Subscribe
100 subscriptions are available per topic. Therefore, you can send 100 messages at the same time suggests..
(There is no guarantee that the nature of the messaing real-time systems).

03. Topic Message
http/https, email, sms form can be transfered as a message.

04. Set topic permissions
You can adjust the subscriber and the sender by own permission settings on your topic.

05. Confirm subscription
In order to verify the accuracy of the delivery of the message, subscription request will be validated by the media at the time of application.
(Confirm Subscribe)

Main Functions

1. create a topic

Topics indicates the particular subject or event type. Topic is to publish a message, or some kind of access point you use when you receive a notification (Notification) (Access point).

2. Set policies on topic

Once a topic is created, the owner of the topic, you can set a policy on the topic. Who is able to issue a message to the topic, who can also subscribe to receive a notification, the topic is such that this policy some protocols (eg, HTTP / HTTPS, Email, SMS ...) whether the support . A topic supports the use of multiple protocols to deliver the notification (Notification) message.

3. Subscribe to the topic (Subscriber) Register

Subscribers (Subscriber) is a client who want to receive a notification from the topics that interest you. Subscribers to receive notifications or subscribe to the topic, the topic owner, you must register. The subscriber specifies the protocol and destination (end-point) used for notification delivery when you signed up. If you are using the HTTP or HTTPS register a URL that can receive messages to the destination and, if you are using the Email and register your Email address as the destination. This is known as subscription request (Subscription Request), and, cloud messaging destination sends a subscription confirmation to the destination in order to verify that valid messages contained in the request (Confirmation Message). The confirmation message can contain the authentication key, the subscriber must tell the key to the cloud messaging. Subscribers can call the direct confirmation API (Confirmation API) to send a confirmation message, and it calls the console commands to process. If the Email has forwarded a link to perform the verification function, subscribers can complete the verification process by clicking on this link.

4. The message publication and notification delivery

When the owner of the topics that they want to be updated about the subscriber Notifiy, user topics from the owner or owner authorized the topic of the message issued will issue a message about that topic. cloud messaging start message sent to all subscribers are available as soon as the message was issued.
Virtual Machine Alert
Option 1.
  • Select Server (CPU/RAM)
  • : Server(VM) 1v core/1G memory
  • Operatoion System
  • :
  • Comment
  • :