Date: Wed, 19 Jan 2000 04:03:33 -0600 (CST) From: Don Read <dread@calcasieu.com> To: James A Wilde <james.wilde@telia.com> Cc: freebsd-questions@FreeBSD.ORG, "Windsor Match Plate and Tool Ltd." <wmptl@MNSi.Net> Subject: Re: M$ Exchange Server Support Message-ID: <XFMail.000119040333.dread@calcasieu.com> In-Reply-To: <002b01bf6259$40b972d0$8208a8c0@iqunlimited.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19-Jan-00 James A Wilde wrote: <snip> > What's the problem with using tasks? Tasks, as far as I can see, is a > client function contained in Outlook, and nothing to do with the server. I > can find no reference in the Exchange Server help file or Books Online > referring to tasks as a server-based function. > MAPI object-ifys everything. a email is a object, an attachment is a object, a task is a object, even the login credentials is an object. The the client _and_ the server has to have knowledge of the structure of all these object classes to store and load; normally thru a common 'mapi.dll', but the boys from Redmond have been know to break it now and again. While you can manage your personal tasks with just the Outlook client, some of the more advanced group scheduling, global address lists, etc requires the MS-Mail / Exchange server /* opinion of a recovering MAPI developer; OALA,EGO */ As Microsoft's documentation on extended-MAPI is useless (I suspect they make it up as they go along), a sane programmer should cower under the desk and wimper at the thought of anything to do with it. Regards, -- Don Read dread@calcasieu.com EDP Manager dread@texas.net Calcasieu Lumber Co. Austin TX -- No Coffee No Peace. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.000119040333.dread>