Le 16 août 11 à 09:39, Mathias Bauer a écrit :
On 16.08.2011 09:27, eric b wrote:
Does this method to allow "OpenOffice.org growing" only ? If we
systematicaly compare to an existing but fixed blob, we have no way
to remove useless/no longer needed services ? (but maybe I
misunderstood )
We can do with that reference file whatever we want, until now we
had the requirement to refrain from incompatible API changes. Some
time ago
we decided that incompatible API changes should be allowed for
future major releases of OOo, so the reference rdb usually would
become the one
of the last major release. There also is an exception list with
"allowed incompatible changes", e.g. removal of superfluous
(unused) types. This
list usually was maintained by the API project lead, Jürgen Schmidt.
Ok I think I understand. So correct me if I'm wrong : at every
build, we compare the just built one with the reference. Any
difference triggers a breaker.
With a cold start, occurs a big and costly I/O read write process.
Searching what seems to cause that, it appears the .rdb files are
good candidates. I can be plain wrong, but I think there are a lot of
services embedded in the interface, who probably could be loaded ...
say somethingl like on demand or at least differently, no ?
Sorry, I don't understand. Are you referring the cold start of the
OpenOffice.org application? That would be a completely unrelated
discussion.
Sorry, I mixed my first question and what I'm currently doing :)
IIRC Stephan Bergmann and/or Matthias Hütsch have worked on
performance improvements regarding types.rdb in the OOo 3.2 release
time
frame.
Yes, and his work interests me.
Thanks,
Eric
--
qɔᴉɹə
Education Project:
http://wiki.services.openoffice.org/wiki/Education_Project
Projet OOo4Kids : http://wiki.ooo4kids.org/index.php/Main_Page
L'association EducOOo : http://www.educoo.org
Blog : http://eric.bachard.org/news
