Separate Server and Client
It might be beneficial for Noise to be able to run in the background independent of it's GUI. This would facilitate things like playing music, syncing, downloading purchases or podcasts, etc all without showing the main window and without having to keep Noise perpetually (what the user perceives as) "open".
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
| Bug #1073871: Monitor library for changes [$55] | Fix Committed |
| Bug #1074168: download podcasts in background | Won't Fix |
| Bug #1074242: Gala can accidentally kill music | Fix Released |
Sprints
Whiteboard
I agree on using separate daemons for device syncing and downloading (https:/
However, I'd prefer to have playing music tied to UI. GStreamer is not *that* complicated to write a music-playing daemon, but communication with the daemon is going to be very complicated, just like HURD is compared to Linux.
Memory usage is not going to drop off a cliff by unloading UI because it's SQLite which consumes most memory (according to kalikiana) and we'll have to keep its data in memory anyway to submit it to the daemon.
--shnatsel
Considering the recent changes done (and more happening) in Noise, and the decision to not have Noise playing a music when closed (or just resume the music). This item won't be applied.
But the downloader-service is a good thing to keep in mind. -- tintou
