新功能要求 |
Enable GCM update option |
| ID: 370Status: 待處理Version: 0.2.5Report Date: 18/05/2016Product: 小鴨幹線 | |
| Reporter | Tom |
| Assignee | |
Description Please implement GCM update function, just like the old studiokuma call filter does |
|
新功能要求 |
Enable GCM update option |
| ID: 370Status: 待處理Version: 0.2.5Report Date: 18/05/2016Product: 小鴨幹線 | |
| Reporter | Tom |
| Assignee | |
Description Please implement GCM update function, just like the old studiokuma call filter does |
|
在〈Enable GCM update option〉中有 3 則留言
If you are referring to the old hotlist (即時名單) function in studiokuma call filter, this requires the real time analysis of newest reported calls, which is only provided to the Call Defender / Studiokuma app (as it always was since the old version), not other apps. It is now only available to the Pro version of Call Defender. This does not seem to be changing any time soon, so there is no way for me to achieve the function in the client side, sorry.
Hi,
What I mean is the GCM push update function. When hkjunkcall.com publishes a new version of database, the app can receive GCM push from your server, and performs update automatically.
The app operation is now server-less (other then this wordpress site). I am working to optimise update time to more closely follow the hkjunkcall server update pattern in the short term, without using push, which hopefully could reduce the delay to around one hour on average (for polling 4 times a day), if hkjunkcall continues to update with a predicable time pattern.
With the above, setting up an app server *just* for daily update notifications does not seem to worth the complications – the daily list is already delayed by 1/2 day on average, and I also need to add artificial delays anyway to clients to avoid a ddos on hkjunkcall (studiokuma uses CDN but my app access hkjunkcall server directly).
I may work on an app server when there is enough users to make a better use of it, but maybe in a longer term.