[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebsoa] Sample Pattern: Receptionist as a Hub
Joseph: The next step is to discuss such on a conference call. The poll closed Friday and it appears that Wed AM is favored: Monday Morning (EST5EDT) 13% Monday Afternoon (EST5EDT) 13% Tuesday Morning (EST5EDT) 9% Tuesday Afternoon (EST5EDT) 4% Wednesday Morning (EST5EDT) 17% Wednesday Afternoon (EST5EDT) 13% Thursday Morning (EST5EDT) 13% Thursday Afternoon (EST5EDT) 4% Friday Morning (EST5EDT) 9% Friday Afternoon (EST5EDT) 4% Duane Chiusano Joseph wrote: >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 >> >> > > > -- Senior Standards Strategist Adobe Systems, Inc. http://www.adobe.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]