Re: Of Bank Tellers...

[Christopher Ferris <chris.ferris@east.sun.com>]

Yes,

I agree that a few use cases will certainly help
to drive home the point that ebXML can easily handle
any model of exchange (RPC, asynch msg, one way, mailbag, etc.)

Chris

dick@8760.com wrote:
> 
> David wrote:
> 
> > Dick - OK - you answered most all my questions now.  I think I'm too
> > fixated on the MIME/SMTP model.
> 
> I expect there will be more ebXML/HTTP implementations than any other
> combination (FTP, SMTP).  The testing we've done internally at 8760 indicates
> that ebXML works well in RPC mode as well as Async messaging mode. Servlets +
> ebXML make a good combination for request/response model, add HTTP access
> controls+SSL and apply encryption/digital signatures to the payload and you've
> got the foundation for a secure, reliable E-Commerce (B2B) platform.
> 
> > Its easy to take that impression away from the current draft - and I would
> > recommend that this is offset later, by introducing more example uses,
> > and clarifications.   Maybe some sample diagrams of interaction modes
> > and network architectures would help here significantly.
> >
> 
> The TR&P group has identified a few use cases to drive the design process. One
> of the cases models a stock price inquiry that is a request/response (RPC)
> processing/programming model. The RPC model is what I believe you would like to
> see explicitly stated as a supported deployment model within the ebXML specs.
> Correct?
> 
> John Ibottson and Ian Jones are planning to expand the number of use cases that,
> I'm assuming, will depict other processing models and/or enhance the existing
> models. Perhaps we should include the use cases in the TR&P requirement spec to
> address David's concerns.
> 
> Dick Brooks
> http://www.8760.com/
> 
> =======================================================================
> = This is ebxml-transport, the general mailing list for the ebXML     =
> = Transport project team. The owner of this list is                   =
> = owner-ebxml-transport@oasis-open.org                                =
> =                                                                     =
> = To unsubscribe, send mail to majordomo@lists.oasis-open.org with    =
> = the following in the body of the message:                           =
> =      unsubscribe ebxml-transport                                    =
> = If you are subscribed using a different email address, put the      =
> = address you subscribed with at the end of the line; e.g.            =
> =      unsubscribe ebxml-transport myname@company.com                 =
> =======================================================================

-- 
    _/_/_/_/ _/    _/ _/    _/ Christopher Ferris - Enterprise Architect
   _/       _/    _/ _/_/  _/  Phone: 781-442-3063 or x23063
  _/_/_/_/ _/    _/ _/ _/ _/   Email: chris.ferris@East.Sun.COM
       _/ _/    _/ _/  _/_/    Sun Microsystems,  Mailstop: UBUR03-313
_/_/_/_/  _/_/_/  _/    _/     1 Network Drive Burlington, MA 01803-0903

=======================================================================
= This is ebxml-transport, the general mailing list for the ebXML     =
= Transport project team. The owner of this list is                   =
= owner-ebxml-transport@oasis-open.org                                =
=                                                                     =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org with    =
= the following in the body of the message:                           =
=      unsubscribe ebxml-transport                                    =
= If you are subscribed using a different email address, put the      =
= address you subscribed with at the end of the line; e.g.            =
=      unsubscribe ebxml-transport myname@company.com                 =
=======================================================================