Jason Tackaberry wrote: >> BUT the result you get could be something you can iterate. But >> something like that is not implemented yet, in fact, I need a sorted >> result list to find changes very fast. So I always need everything. > > Can you elaborate on this? > > At least for a non-directory query (keyword search, artist search, etc.) > this can be returned incrementally to the client and we really should > support that. Otherwise there is absolutely no reason (and no need) to > ever return InProgress inside kaa.db.
I need that in kaa.beacon.db. The reason is directory sort. A listdir can block and stuff like that (and a sorted result is much faster). So the server needs to be aware that what can block. kaa.db itself should not change. We could add support to the _client_ side that an artist query returns only x items at first, but that has nothing to do with the server and I'm only hacking on the server right now. IMHO the server should always get everything, otherwise it can not monitor changes. Dischi -- Students nowadays, complaining they only get 5MBs of disk space! In my day we were lucky if we had one file, and that was /dev/null.
pgpcRZeHPx7oH.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Freevo-cvslog mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-cvslog
