<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Scott, thank you for your response. I have some questions related:</div><div><br></div><blockquote type="cite"><div>Couple of thoughts:<br><br>- I wouldn't expect you'd ever touch relying-party.xml if your use case is<br>provisioning SPs. That should rarely be needed.<br></div></blockquote><div><br></div><div>At the moment I'm running some tests with Google Apps and I am provisioning SPs as this document mentions:</div><div><a href="https://developers.google.com/google-apps/help/articles/shibboleth2.0">https://developers.google.com/google-apps/help/articles/shibboleth2.0</a> where the SPs are included in the</div><div>relying-party.xml, but you said using this file is rarely needed, can you please explain a little more about it?</div><div><br></div><blockquote type="cite"><div>There may be interactions between your proposed reaction to a failure and<br>the normal way the code deals with preventing corrupt config objects from<br>replacing live/working ones. Maybe you're operating at a level that would<br>supersede that, I'm not sure.<br></div></blockquote><div><br></div><div>Well, I'm only catching the ServiceException, if something goes wrong, during the reload </div><div>of the services (using the HttpServletHelper class) I trigger the operation of replacing the</div><div>original and valid configuration files for the bad ones (the step 9 of my previous email), but this</div><div>is something I want to leave it to Shibboleth, I mean, call the methods and classes Shibboleth uses </div><div>to handle this situation, instead of trying to recover from a failure by copying and replacing the files myself. </div><div><br></div><div>Right now I'm studying the way Shibboleth, like you said, prevents corrupt config objects from replacing </div><div>live/working ones, in order to do this the right way. </div><div><br></div><blockquote type="cite"><div>Right, well, the other feedback is that all the work is in concurrency<br>safety.<br></div></blockquote><div><br></div><div>I'm little confuse here, so I'll explain myself through two examples:</div><div><br></div><div>1) Since Shibboleth can be setup to reload the configuration files by time intervals; let's say for example,</div><div>that I start working with the files (reading, copying) and precisely in the middle of my operations, Shibboleth </div><div>starts reloading the files (because the time interval matches the time) through the services (HttpServletHelper)</div><div>and since Shibboleth puts a Lock, If I didn't put a Lock first, I believe a problem will occur. </div><div><br></div><div>So I'm looking for a way in which I can put a Lock or use Shibboleth to put a Lock in order to prevent </div><div>any problems.</div><div><br></div><div>2) I'm designing the provisioning of SPs to be dynamic and that it can be done by multiples users at the same time,</div><div>so I working in putting a Lock to prevent concurrency issues.</div><div><br></div><div>Can you please elaborate a little more about what you said, taking into account what I have wrote?</div><div><br></div><blockquote type="cite"><div>Sounds pretty interesting in general, though. Might be the seeds of a<br>service interface we could incorporate or package as an extension and<br>would be great code to have as an example.<br></div></blockquote><br></div><div>Great! :) As soon as I can (it might take me some weeks, due to my job) I will create a document where I'll explain everything I have done related to the information</div><div>in these e-mails and I'll attach the code.</div><div><br></div><div><br></div><div>Thanks again Scott for all your help. I really appreciate the time you and other people take to answer the questions and doubts.</div><div><br></div><div>Best Regards!</div><div><br></div><div>-Mark</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>