Difference between revisions of "WEB PUSH GFMS"
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
---- | ---- | ||
| − | As users need automatic generated updates on their AOI for their products a Web-Push Notification and | + | As users need automatic generated updates on their ''AOI'' for their products a Web-Push Notification and e-mail service for registered users will be implemented. <br> |
The services follow an open paradigm, making it compatible with current web browser technologies. <br> | The services follow an open paradigm, making it compatible with current web browser technologies. <br> | ||
After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the [[ REST_API_GFMS | '''REST-APIs''']]) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not. | After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the [[ REST_API_GFMS | '''REST-APIs''']]) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not. | ||
| Line 13: | Line 13: | ||
[[File:webpush.jpg]] | [[File:webpush.jpg]] | ||
| + | |||
| + | |||
| + | Whenever [[PRODUCTS | GFM's products]] are delivered from the EO-process chain, the metadata about the products are stored in the meta-data database ('''A'''). <br> | ||
| + | A periodic notification job, executed every 5 minutes, checks the product catalogue in the meta-data database according to the ordered notifications ('''B'''). <br> | ||
| + | If a notification must be issued due to the user’s request, the appropriate notification is pushed into a message queue ('''C'''). | ||
| + | |||
| + | |||
| + | [[File:webpush_logic.jpg]] | ||
| + | |||
| + | |||
| + | Each time the user logs-in, the database will be scanned for new notifications since the last access. If undelivered notifications are present in the system, they will be sent to the queue and hence to the client’s web browser by means of a full duplex web socket connection. | ||
---- | ---- | ||
[[GFMS | [Home]]] - [[DATA ACCESS | [DATA ACCESS]]] | [[GFMS | [Home]]] - [[DATA ACCESS | [DATA ACCESS]]] | ||
Latest revision as of 12:59, 17 June 2021
As users need automatic generated updates on their AOI for their products a Web-Push Notification and e-mail service for registered users will be implemented.
The services follow an open paradigm, making it compatible with current web browser technologies.
After a registered user or administrator has ordered a notification for a given AOI and product (e.g. via the REST-APIs) the backend will notify the user by means of an e-mail and/or whenever the user logs into the portal via a push notification, which will be displayed at his device, regardless if mobile or not.
As highlighted in the figure below the user will get a notification about the updated availability of his product at Login at the GFM Portal.
The notification will inform the user about the temporal aspect of the ordered product and the access options (e.g. download link, map server access for WMS-T, metadata, et c.)
Whenever GFM's products are delivered from the EO-process chain, the metadata about the products are stored in the meta-data database (A).
A periodic notification job, executed every 5 minutes, checks the product catalogue in the meta-data database according to the ordered notifications (B).
If a notification must be issued due to the user’s request, the appropriate notification is pushed into a message queue (C).
Each time the user logs-in, the database will be scanned for new notifications since the last access. If undelivered notifications are present in the system, they will be sent to the queue and hence to the client’s web browser by means of a full duplex web socket connection.
