You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we have JSON forum lists and stuff now, and we can run the checker task (I'll push it soon) more often now since it's just one page of data, it might be cool to spin that stuff off into a background service of some kind. Nothing fancy, just a component that does its own thing, runs update tasks for whatever on its own schedule, and the main app can connect to it for updates
Right now it runs on startup, and some app pages poke it and tell it to sync a thing, so it would be nicer if it just handled it itself. It would be easier to schedule tasks, you could have more of them (like checking for PMs, updates to bookmarked threads etc) and we could potentially have it run while the app isn't in focus or running, pop up notifications and stuff
That's all future ideas, but I think an independent sync component would be neater for the stuff we're doing right now anyway
The text was updated successfully, but these errors were encountered:
Since we have JSON forum lists and stuff now, and we can run the checker task (I'll push it soon) more often now since it's just one page of data, it might be cool to spin that stuff off into a background service of some kind. Nothing fancy, just a component that does its own thing, runs update tasks for whatever on its own schedule, and the main app can connect to it for updates
Right now it runs on startup, and some app pages poke it and tell it to sync a thing, so it would be nicer if it just handled it itself. It would be easier to schedule tasks, you could have more of them (like checking for PMs, updates to bookmarked threads etc) and we could potentially have it run while the app isn't in focus or running, pop up notifications and stuff
That's all future ideas, but I think an independent sync component would be neater for the stuff we're doing right now anyway
The text was updated successfully, but these errors were encountered: