On Thu, 2013-12-19 at 15:01 -0500, Kohei Yoshida wrote:
So, my preferred solution in this case is to optimize
the libebook's detection service, rather than playing around the order
of detection services to avoid this particular scenario.
Quite :-) doing lots of small reads (or writes) from an XStream (or an
IStream on windows) introduces some significant performance problems
whatever we do; it'd be great to have a nice caching stream
implementation to wrap / proxy such things I guess.
ATB,
Michael.
--
michael.meeks@collabora.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.