bluegaspode;620427 Wrote: > I'm looking at the comet command (i.e is it 'albums' or 'artists') and > then create a lookup-key from all params. Thus I'm also caching albums > for a specific artist or albums of a genre, ... > Now every command is 'browselibrary' and without knowing all possible > keys I might get ambiguous keys.
That is not going to work. You are not going to be able to work out what kind of list you are looking at by using the command used to obtain the list. To start with BrowseLibrary has a server-side API that facilitates augmenting, restricting or replacing completely the menus available under My Music, including using commands and callbacks that you have no chance of interpreting. Basically, the SlimBrowse protocol is not designed to facilitate content-knowledegable caching. It is a menu-presentation protocol, not a data-delivery protocol. I know that several people such as yourself would like the like the latter but that is not what it is. The UI model is implemented on the server, not the client. The client only provides the skin. If you want to implement the model in the client then I guess you need to use the raw CLI commands (albums, artists, etc., not in menu mode). -- awy ------------------------------------------------------------------------ awy's Profile: http://forums.slimdevices.com/member.php?userid=7480 View this thread: http://forums.slimdevices.com/showthread.php?t=85895 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
