Subject: MORE: Re: WebDav?
Farrukh, OK - I'm pleased with this outcome - I just wanted a sanity check before launching out to the wider world. For my money the http transport with XML structure is the default for RegRep. I really do not want to contemplate accessing a Registry via SMTP, as all use cases really indicate a real-time linkage. We can share aspects such as security profile, TPA profile, and metadata tags and definitions where appropriate so there is a high degree of commonality with TRP headers. However, the other functional side of things is clearly well support by WebDav and so a blend and best-of-breed approach beckons here.... and especially the possiblity of saving a considerable amount of time and effort by adopting those components that deliver the business functions we require. Thanks, DW. =========================================================== Message text written by INTERNET:Farrukh.Najmi@east.sun.com > Upon reading up on WebDav it seems that at the very least we should learn from its DASL (DAV Searching and Locating) protocol as well as locking/version control protocol (post November functionality). If any one has experience with WebDav or similar protocols, please share. -- Regards, Farrukh > >David, > >Thanks for the suggestion. I will look into it. BTW I must insist again that >we should have these conversations on the regrep list since I want us to engage >as a team, in a proper context and a specific purpose. For instance if anyone on >the >team has knoweldge of WebDav they can chime in. > >My initial think on WebDav is that it is an HTTP based technology, I prefer >eating our >own dog food and having all access to an ebXML registry be based on ebXML >transport. I was assuming this to be a high level design principal. Comments >anyone?<
eList eXpress LLC