Hi, The EU TESS program (social security sector) is using its own implementation of ebMS over FTP i a pilot program. The program uses a standard, central FTP server where files are transferred. If that is of interest, I can dig up some more information as I am part of that TC. Except for the custom-built TESS ebMS software, I haven't seen any COTS ebMS over FTP solutions. Regarding ebXML transport protocol bindings, experience shows that every implementation supports HTTP/S as it is the minimum conformance requirement. SMTP only gained momentum whem actual cases required it. Using the Internet, ebMS over SMTP proves to be a challange for SPAM filters and vice versa. I attribute differences in various ebXML specification to the fact that these were developed by different groups. Matter of factly, I cannot see any limitations as to which transport protocol might be specified/used/implemented. X.400 and MQ come to mind, although each does a lot of what ebMS does to begin with. Substantial cost might be attached to such (ad)ventures, as this issue quickly reveals design time shortcuts in imlementations; i.e. am ebMS implementation not designet to actually support anything but HTTP/S might run into difficulties. At least FTP can be 8 bit clean in binary mode, thus relieving the implementation of special adaptations like transfer-encoding or line length limitations as with SMTP. ebXML and to some extent ebMS' independence of the actual transport is exactly what I like about the stack. Still, I have yet to see a full blown ebCPPA+ebMS supporting the "P" in TRP, anything but trivial security profiles including actual PKI support, not just PKC, and as You ask, a wider range of transport adapters. best regards Torsten > -----Opprinnelig melding----- > Fra: Pim van der Eijk [mailto:lists@sonnenglanz.net] > Sendt: 15. juli 2004 14:19 > Til: ebxml-dev@lists.ebxml.org > Kopi: 'Bryan Rasmussen'; 'Matthew MacKenzie' > Emne: FTP protocol support and use > > > > Hello, > > On a related note, in a customer environment, FTP is the de > facto app-to-app data exchange protocol. > It is used in several large scale production systems, is > supported by the network management > organization, allowed through gateways/firewalls etc. To > introduce a technology like ebXML Messaging > here, the ability to leverage this infrastructure would be an > advantage. > > I noted that whereas the CPPA specification (section 8.4.38) > seems to treat FTP as a supported > protocol on a same level as HTTP and SMTP and has several > useful guidelines, the ebXML Messaging > specification (appendix B) only discusses bindings to HTTP > and SMTP. I am interested in learning > about any issues with FTP one should be aware of, in > particular interoperability issues. > > Also, I would appreciate (anonymized) pointers to deployed > ebMS solutions that use ebMS over FTP. > > Kind regards, > > Pim van der Eijk > > -----Original Message----- > From: Matthew MacKenzie [mailto:matt@mac-kenzie.net] > Sent: Thursday, July 15, 2004 1:16 PM > To: Bryan Rasmussen > Cc: ebxml-dev@lists.ebxml.org > Subject: Re: message service agnosticism and http bindings > > Bryan, > > My experience is that HTTP is definitely the leader in usage, > but SMTP is also used fairly often. > Other protocols are on the fringes, mostly because we don't > define how to bind them in the > specification. > > Regards, > Matthew MacKenzie > Sr. Architect, Adobe Systems > Editor, OASIS ebXML Messaging TC > > > On 15-Jul-04, at 6:17 AM, Bryan Rasmussen wrote: > > > > > Anyone have any in the field observations as to how often > http is used > > for the message service and how often other protocols? If there are > > any particular protocols that are widely used in > competition with http > > in this case I would appreciate a note. > > > > The ebxml-dev list is sponsored by OASIS > <http://www.oasis-open.org> > > The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > > To subscribe or unsubscribe from this list use the subscription > > manager: > > <http://www.oasis-open.org/mlmanage/> > > > > > The ebxml-dev list is sponsored by OASIS > <http://www.oasis-open.org> The list archives are at > http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the > subscription manager: > <http://www.oasis-open.org/mlmanage/> > > > > > The ebxml-dev list is sponsored by OASIS > <http://www.oasis-open.org> The > list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the > subscription manager: > <http://www.oasis-open.org/mlmanage/> >
<<attachment: winmail.dat>>