> This algorithm would hold the "D" until "A", "B", and "C" had been > received and processed. > ... > Whether this approach is suitable or appropriate in the business > processes context I do not know.
Yes, that is more my question. I would not expect this to be part of a business-level "choreography". At a lower, implementation level, certain protocols would require fixing up the proper business-level ordering. I'd hate to see higher-level code dealing with lower-level technical details however. -Patrick ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/WktRrD/lOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
