Menu
▾
▴
Re: [ebxmlms-develop] Hermes 1.0: CPA
|
From: Patrick Y. <kc...@ce...> - 2003-07-10 10:41: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 text="#000000" bgcolor="#ffffff"> <br> <blockquote type="cite" cite="mid...@po..."> <div><span class="839050200-10072003"><font face="Arial" color="#0000ff" size="2">It says the 'messaging service layer'. It never says the 'sending msh' sould prevent sending messages that do not conform to the cpa, although this seems good practice to me. Otoh it only states "Any violation of the ground rules result in an error condition, which is <font size="2"><font color="#0000ff"><font face="Arial">reported using the appropriate means.</font></font></font>".</font></span></div> <div> </div> </blockquote> The point is now: should the sending MSH checks the message to be sent is compliant to CPA or not. Obviously this depends on whether the sending MSH knows about the CPA (or its parameters) or not. My original thinking is not for that... to simplify the registration process. <br> <br> Of course, I agree that adding those checkings make Hermes clearer. So, if this is agreeable, we need to add the interface for client application to specify CPA parameter in the sending object. Each message sending through that sending object will got checked againist the parameter.<br> <br> What do you think?<br> <br> <blockquote type="cite" cite="mid...@po..."><font face="Times New Roman"></font><span class="839050200-10072003"> <div align="left"><font face="Times New Roman"> </font><span class="839050200-10072003"><font face="Times New Roman"><font face="Arial" color="#0000ff" size="2">maybe we should have an onError(), onNotify() as wel in the url/file/jms/... providers e.g. for reporting back the things Patrick summed up (acks etc) but also asynchronous reporting of 'your message does not comply with this cpa' and other stuff. The onMessage, onError etc, could all go over different channels, but I'm not for that. Different url's (but all url's) or different directories (but al directories) seems ok to me <br> </font></font></span></div> </span></blockquote> <br> To make it more generic, we propose to allow applications to register (i.e. subscribe) to different channels for receiving those things. All channels should provide a onMessage() method.<br> <br> Regards, -Patrick<br> <br> <br> <br> </body> </html> |
