Warning: Can't synchronize with the repository (Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.

Ticket #33 (closed enhancement: wontfix)

Opened 3 years ago

Last modified 3 years ago

implement daapstream for sending x-dmap-tagged responses

Reported by: msfrank Owned by: msfrank
Priority: minor Milestone: 0.2
Component: daap Version:
Keywords: Cc:

Description

we could make daap responses more efficient by streaming the output instead of generating the entire response before writing. this would have the biggest effect on the ListItemsCommand?, which can generate a very large response if the database has lots of items.

Change History

Changed 3 years ago by msfrank

  • status changed from new to closed
  • resolution set to wontfix

closing this as wontfix. given that the daap protocol doesn't make it possible to stream the data to clients without knowing the size of the entire message (since dmap containers need to know the size of their children), we can't start streaming until the whole response is built. all this code would buy us is less memory used, which is a noble goal but probably a premature one. a better way to save us some time would be to cache the result of the ListItemsCommand? and use that until we get notified that the database has changed.

Note: See TracTickets for help on using tickets.