RE: MAPI or WebDAV

Hi

I've developed a mail system based on WebDAV,
I'm still not sure which way is the best..

We run front-End Server and Back-End Server together, Under this Front /
Back End Configurations, I heard that I should use WebDAV to locate the
applications in front-End Server, so that anybody who can use internet could
access the system.

Like you said, It is OK to use ADO,CDO,ExOleDB to get date from exchange
server, but I heard it's possible when the applications locate in the same
Exchange Server. You can use the MS Server XMLHTTP technology to build your
application based on WebDAV, and I am sure you can find the samples from
Exchange SDK.

For the second question, the answer is Yes.

I hope this would help you a little. :-)

Elly Kim

"Raghu"님이 작성한 내용:

> Hello,
>
>
> I am in the process of evaluating which is the best technology to talk
> to Exchange server and basically questioning whether go for MAPI or
> WebDAV.
>
>
> To my understanding MAPI is the most native way to talk to exchange
> server and WebDAV interacts with Exchange server via http calls. I have
> the following questions wrt WedDav based interaction:
>
>
> (a) WebDAV makes http calls to be handled by IIS (installed in the same
> system where exchange server is installed). Can someone tell me what
> technology is used by IIS to interpret the WebDAV calls (does it use
> EXOleDB/MAPI/CDO to finally fetch data from exchange store OR is it
> something different ?) ?
>
>
> (b) Can WebDAV work with IIS which is not installed in the same system
> where exchange server is installed ? (if it uses ExOleDB internally as
> its native technology then i guess ExOleDB cannot be used to extract
> info from a remote exchange server)
>
> Considering synchronization (synchronization of groupware items between
> legacy system and Exchange server) scenario and collaboration (legacy
> system having its own UI infrastructure to show information from
> Exchange server) scenario, which is the best technology one can use to
> interact with Exchange Server (i.e. is it MAPI or WebDAV) ?
>
>
> best regards,
>
>
> Raghu
>
>
.

Relevant Pages

  • [NT] Vulnerability in WebDAV XML Message Handler DoS (MS04-030)
    ... Get your security news from a reliable source. ... send a specially crafted WebDAV request to a server that is running IIS ... Mitigating Factors for WebDAV Vulnerability ...
    (Securiteam)
  • Re: WebDAV disabled!
    ... but the Web Service Extension named WebDAV is nothing to do with OWA - ... that extension enables WebDAV on the entire server, ... Look at the properties of the Microsoft Exchange Server ...
    (microsoft.public.exchange.admin)
  • Re: Manage public folders from .NET
    ... You can also manage public folders using WebDAV protocol. ... If you need WebDAV API for Exchange server, ...
    (microsoft.public.exchange.development)
  • Re: Manage public folders from .NET
    ... You can also manage public folders using WebDAV protocol. ... If you need WebDAV API for Exchange server, ...
    (microsoft.public.exchange2000.development)
  • Re: URLScan Logs
    ... I'm not a webdav expert, ... > Front Page server extensions are not configured for the> site. ... I have been experimenting with locking down this> IIS server and have the latest patches on it and have> followed many of the procedures outlined in several guides> including "From Blueprint to Fortress: A Guide to> Securing IIS 5.0". ... > contains disallowed header 'translate:' Request will be> rejected. ...
    (microsoft.public.inetserver.iis.security)
Loading