Hi, On Tue, Nov 2, 2010 at 1:56 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > Did you actually check if tracker/sparql doesn't support having a byte > limit instead of contact/row? I know this sounds crazy, but Ive seem > some other implementations of pbap that does similar things as to > query a number of contacts and they can cause big pauses when > generating the responses depending on the size of the MTU being used > and in fact doesn't completely eliminate the extra buffering on the > plugin side. Also I think we might need to use the read callback to > continue the queries and not do it regardless of the speed the client > can read, otherwise we may run in the same situation as we have now > but instead of asking all the data at once we do it in parts but we > still don't care if the client is fetching that data at the same pace > we buffer. Radek and I discussed this offline and came to a conclusion that using a temporary files to buffer the data is probably a better idea, first because it will be difficult to synchronize the speed of client and backend which can either cause too much buffering (OOM) or slow transfer speed, the second reason is that if we start supporting avatar/image then each contact will probably consume a lot more memory than it does right now and third caching can probably be done much more efficiently using temporary files. -- Luiz Augusto von Dentz Computer Engineer -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
