[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebsoa] Sample Pattern: Receptionist as a Hub
Thanks Matt. Applying this to technology and integration, I believe the rough equivalent would be an integration broker. If folks agree, what would be the next step given our charter? To show how an integration broker can be used within an architecture to communicate between (for example) 2 ebXML-based* systems, or perhaps from a non-ebXML-based system to one that is? Just trying to get an early sense of where this patterns path could take us, before we go too far with it. Joe *we would need to define what "ebXML-based" means, of course Matthew MacKenzie wrote: > > Here is an example of a "Pattern". Patterns can be defined for all kinds of processes, not just software development. We may have to do a bit of research on what an appropriate pattern language would be for our work, but this is a good example. > > http://www.comp.lancs.ac.uk/computing/research/cseg/projects/pointer/patterns/receptionistAsAHub/receptionistAsAHub.html > > ___________________________ > Matthew MacKenzie > Senior Architect > IDBU Server Solutions > Adobe Systems Canada Inc. > http://www.adobe.com/products/server/ > mattm@adobe.com > +1 (506) 871.5409 -- Kind Regards, Joseph Chiusano Associate Booz | Allen | Hamilton
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]