Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 10 Apr 2008 08:46:01 -0700,    group: microsoft.public.exchange.clients        back       


Which Exchange technology to chose.   
Hope you can help me on this one. 


I've been assigned the small (?) task of building the following application:
 
- The application is be able to read all information for all users on a 
given Exchange Server.
- The application may be deployed on other machines than the Exchange Server 
itself. 
- The application will eventually be distributed to clients as a Windows 
Service.


I've been looking at various technologies for reading from an Exchange 
Server. 

ADO: Server side only.
CDO + EX(M): Server side only.
WebDAV: Not that widely supported. 
Extended MAPI: Requires an installed MAPI client w. user profile.

These findings may or may not be right, by the way. Please feel free to 
comment. My sources sometimes disagree.


So i apparently have to choose between Extended MAPI and WebDAV. Are there 
any pros and cons i've overlooked. Or possible solutions i've missed? 
Programming language and/or developement platform is of minor importance.

Thanks in advance,
Søren
date: Thu, 10 Apr 2008 08:46:01 -0700   author:   Soren Turin

Re: Which Exchange technology to chose.   
"Soren Turin"  wrote in message 
news:45AB3238-71A4-470C-93CF-101A6570AFD1@microsoft.com...
> Hope you can help me on this one.
>
>
> I've been assigned the small (?) task of building the following 
> application:
>
> - The application is be able to read all information for all users on a
> given Exchange Server.
> - The application may be deployed on other machines than the Exchange 
> Server
> itself.
> - The application will eventually be distributed to clients as a Windows
> Service.
>
>
> I've been looking at various technologies for reading from an Exchange
> Server.
>
> ADO: Server side only.
> CDO + EX(M): Server side only.
> WebDAV: Not that widely supported.
> Extended MAPI: Requires an installed MAPI client w. user profile.
>
> These findings may or may not be right, by the way. Please feel free to
> comment. My sources sometimes disagree.
>
>
> So i apparently have to choose between Extended MAPI and WebDAV. Are there
> any pros and cons i've overlooked. Or possible solutions i've missed?
> Programming language and/or developement platform is of minor importance.
>
> Thanks in advance,
> Søren

You can send WebDAV calls from any Windows PC using the WinHTTPRequest 
object.  Don't know what the equivalent is for non-MS OS's.  Probably the 
easiest to use, too, since it only requires HTTP ports open between client 
and server.

Lee.

-- 
______________________________________

Outlook Web Access For PDA , OWA For WAP
www.leederbyshire.com
email a@t leederbyshire d.0.t c.0.m
______________________________________
date: Thu, 10 Apr 2008 17:02:36 +0100   author:   Lee Derbyshire [MVP] email a@t leederbyshire d.0.t c.0.m

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us