[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Dynamic (late) binding proposal - take 2 now with diagram
Please find the following diagram outlining one way of formulating dynamic or late bound TimeToPerform or similar parameters. At the top there is a abstract superclass that does not turn up in the document, the concrete subclasses does. The BindingTime speficies when binding occurs, i.e. which collaborationEvent(s). (maybe this should also be an element?) Default value is the value before binding occurs TTP duration can be ORed together with Union. <TimeToPerform boundWhen="enclosingCollaborationInitiationEvent"> <Union> <StaticTimeToPerform>2h<StaticTimeToPerform> <RequestMessageTTP>//MessageEnvelope//ResponceTime</RequestMessageTTP> </Union> <TimeToPerform> This patterm may be used for other parameters that are candidates for dynamic binding.. /anders -- ///////////////////////////////////// / Business Collaboration Toolsmiths / / website: <www.toolsmiths.se> / / email: <anderst@toolsmiths.se> / / phone: +46 8 562 262 30 / / mobile: +46 70 546 66 03 / /////////////////////////////////////
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]