Hi, that was indeed an oversight, since I had used
Dim
config As System.Configuration.Configuration = WebConfigurationManager.OpenWebConfiguration("~/")
which is not allowed in medium trust. Interestingly enough, DotNetNuke sees no problems updating the web.config, so I used the same XML based logic to provide an update. I've tested it successfully in medium trust environment at my place.
I guess that so long as DNN needs edit permission on the Web.config file, hosters will have to do with keepalive. At least this solution should be quiet enough no to bring to much attention (as compared to heavy pinging the site).
BTW, if by any chance you get physical access to your web.config file, the only code that the module form does is adding the following node in the HttpModules section, so you could very well do that yourself:
<
add name="Aricie.DNNPaceMaker" type="Aricie.DNN.DNNPaceMaker.Business.PaceMaker" />