Menu
▾
▴
Re: [ebxmlms-develop] Static registration
|
From: Patrick Y. <kc...@ce...> - 2003-06-13 08:18:51
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body> It's a good idea to group our discussions into threads of different topics. :-)<br> <br> <blockquote type="cite" cite="mid...@s-..."> <p><font size="2" face="Arial">The registration you're talking about here is not dynamic registration, but updating the static registration.</font> </p> <p><font size="2" face="Arial">As I said in the "Authentication + authorisation" email, there should be a difference between user level privileges and admin level privileges. Clearly a normal user should not be allowed to modify the registration database.</font></p> </blockquote> Agree.<br> <br> <blockquote type="cite" cite="mid...@s-..."> <p><font size="2" face="Arial">The MSH should have a "load new registration map" command. Naturally this command is invoked as part of the MSH startup. There's also nothing stopping an admin level user from invoking it at any other time after manually editing the registration map.</font></p> </blockquote> You mean: to make a new registration, we have to modify the property file to update the registration map. And then call the MSH reload registration map command to get it known. Right? If the registration is to be done by an upper layer software, I prefer to use the methods you describe in the following...<br> <br> <blockquote type="cite" cite="mid...@s-..."> <p><font size="2" face="Arial">Throw in add/delete/list methods for maintaining the static registration database (only allowed for the admin user), where the add and delete methods do a "load new registration map" automatically, and there you are.</font></p> </blockquote> Now, MSHConfig table is used to maintain it. In view of both ways of registration (by editing properties file and calling methods directly), therefore I suggested to keep on using MSHConfig, i.e. to use DB to keep it accurate.<br> <br> <blockquote type="cite" cite="mid...@s-..."> <p><font size="2" face="Arial">There are a few checks to be made. For instance, you're not allowed to delete a CpaId registration if there is a message pending to be delivered to that CpaId, but nothing complicated.</font></p> </blockquote> <br> Agree. The current unregistration mechanism has already considered this.<br> <br> <br> Regards, -Patrick<br> </body> </html> |
