[GH-ISSUE #38] Support delay message? #32

New issue

Closed

opened 2026-03-03 11:55:32 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 11:55:32 +03:00

Owner

Originally created by @hyorigo on GitHub (Feb 12, 2021).
Original GitHub issue: https://github.com/Finb/bark-server/issues/38

What about the three types of delay message:

Delay - Send to client after X seconds
Schedule - Send to client on scheduled time
Repeat - Send to client for every X seconds or scheduled time repeatedly, ends after Y times or until exactly time

Originally created by @hyorigo on GitHub (Feb 12, 2021). Original GitHub issue: https://github.com/Finb/bark-server/issues/38 What about the three types of delay message: * Delay - Send to client after X seconds * Schedule - Send to client on scheduled time * Repeat - Send to client for every X seconds or scheduled time repeatedly, ends after Y times or until exactly time

kerem closed this issue

2026-03-03 11:55:32 +03:00

kerem commented

2026-03-03 11:55:33 +03:00

Author

Owner

@mritd commented on GitHub (Feb 21, 2021):

There seems to be no relevant description in the APNS official documents. If APNS does not support this feature, the bark server will not implement it.

Because bark server may run in embedded devices, custom features will occupy higher resources and bring more complex problems; the goal of bark server is to serve as a standard api server to provide reliable push APIs for bark app.

The custom scheduling scheme should be implemented by the caller instead of relying on the bark server.

@mritd commented on GitHub (Feb 21, 2021): There seems to be no relevant description in the APNS official documents. If APNS does not support this feature, the bark server will not implement it. Because bark server may run in embedded devices, custom features will occupy higher resources and bring more complex problems; the goal of bark server is to serve as a standard api server to provide reliable push APIs for bark app. The custom scheduling scheme should be implemented by the caller instead of relying on the bark server.