[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [sca-policy] NEW ISSUE: Is binding.sca always present?
From: Anderson, Jeff T (CA - Toronto) [mailto:jeffanderson@deloitte.ca]
Sent: Wednesday, Sep 26, 2007 6:26 AM
To: Patil, Sanjay; sca-policy@lists.oasis-open.org
Subject: RE: [sca-policy] NEW ISSUE: Is binding.sca always present?Are we sure that this should be part of the policy specification? As opposed to the binding specification?
From: Patil, Sanjay [mailto:sanjay.patil@sap.com]
Sent: Wed 2007-09-26 04:32
To: sca-policy@lists.oasis-open.org
Subject: [sca-policy] NEW ISSUE: Is binding.sca always present?
TARGET: SCA Policy Framework
DESCRIPTION: It is not clear whether presence of binding.sca can always be assumed for internal wires, specifically when standard bindings are associated with either end of that internal wire.
PROPOSAL: Add the following semantics to the specifications:
For internal wires, it should always be possible to use bindings.sca regardless of which standard bindings are associated with that internal wire. In particular:
A> When a component service uses a standard binding (e.g. binding.ws), it should be possible for a client from anywhere (with right permissions, etc) to communicate with that service using the standard binding, irrespective of whether that component service is promoted to the domain level or not.
B> It should always be possible to use binding.sca for internal wires, irrespective of which standard bindings, if any, are associated with either end of that internal wire.
************************************************************************************** Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information confidentielle: Le présent message, ainsi que tout fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; il est de nature confidentielle et peut constituer une information privilégiée. Nous avertissons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci. **************************************************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]