> Le 5 janv. 2018 à 15:43, Thomas Schnurrenberger <t...@gmx.net> a écrit : > > On 03.01.2018 23:33, Florian Balmer wrote: >> The startup delay for `fossil ui' and `fossil server' on Windows XP is >> more obvious than possibly sluggish browser navigation, which I >> *think* is due to waiting for StartServiceCtrlDispatcherW. This could >> be cut down by skipping the call to StartServiceCtrlDispatcherW for >> the `ui' and `server' commands, as Fossil always runs in a console >> session, and not as a service, in these cases. >> > I measured the time it takes to call StartServiceCtrlDispatcherW on my > 8 year old Windows 7 64bit box: roughly 600 microseconds, I don't think > this is noticeable!
But on XP the delay is 'intolerable' rather than unnoticeable. :) A small patch for that is included along a larger IPv4/IPv6 patch I submitted today. I see Richard put it on trunk (see [e506ebb764]) minutes ago. Especially those of you using Windows XP would help by building from that code and see how it goes for them. It looks good, and does not require anymore to install IPv6 support (command 'ipv6 install') on Windows XP. The solution is IPv4/IPv6 agnostic. If at least one of both protocols are useable, the software should work nicely. As I'm responsible for asking for this support and did a fair part of that coding, I'll stay alert on issues that would come out, in order to quickly help, should it happen. -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
