Mobile Online Game Development Guide-payment interface-data transmission after receiving the payment notification

Agent 'K will introduce in this article: The user payment interface in Mobile Online Game Development transmits data after receiving the payment notification. (This article is from the edas agent 'K. For more information, see)

For more information about the payment interface, see Mobile Online Game Development Guide-payment interface.

As stated in the payment interface, the payment provider calls back the notification address of the game manufacturer after the payment is successful, in the HTTP format. Gaming serversProgramAnd authentication server programs are not web applications. How can we transmit data between the web program processing paid notifications and the game program?

Agent 'K recommends that you think about it before reading the following content to avoid interference and restriction on your thinking.

Okay, let's say you're done.

The solution is as follows (the order of appearance is irrelevant to the degree of Recommendation ):

1. Embed Web Services in the authentication program (for example, Java programs can embed jetty), so there is no data transmission problem.
2. The web program performs logic processing on its own, and notifies the authentication program after completion (a common method is to send a notification through a socket connection ).
3. The web program does not perform any logic processing. It directly sends the post data or get query string to the authentication program.
4. The web program saves post data or get query strings to the database, and the authentication program regularly queries and processes them.

The disadvantage is that the payer may require that the callback address be at port 80. If you already have or will need to deploy Web applications in the future, you obviously have no choice: solution 1 is impossible; solution 2 and solution 3 require web programs to easily perform socket connections.

If you think of other solutions, please share them.

(This article is from the edas agent 'K. For more information, see)