In Exchange 12 (“E12”), we have focused our public API story on:
Web Services for accessing information stored on the server
Managed Agents for processing mail flowing through the serve...
Updated Jul 01, 2019
Version 2.0
Blog Post
Well, now that someone from the Mac BU's said something, i'm not as concerned. I didn't think these changes would mean you guys got banned from talking to Exchange. I'm not reading doom and gloom, I'm asking for clarification before the noise on this gets higher.
But, and you know a lot of this already, getting this kind of information out of y'all is sometimes a bit...tedious?
However, since you're going to be using DAV primarily in E'rage 12, then what does this rather confusing sentence mean:
"The introduction of the new web services has freed us to “de-emphasize” three of the APIs introduced in previous generations of Exchange. These de-emphasized API’s will be fully supported in E12 (i.e. existing applications will work unchanged), and will be supported for 10 years after E12 releases, based on our standard Microsoft Support Lifecycle. These APIs may not be in future releases of Exchange beyond E12."
Does this mean no more DAV in Exchange post - 12, or that it's going to be there until 2015 regardless of version?
How are the APIs that won't work at all affect Entourage?
What does "work unchanged" mean? Is it a freezing of capabilities of that API ("nothing new will be available to DAV in E12"), a limited set of features ("these new features will be available to DAV, but no others").
Saying "support for ten years" and then in the same sentence saying, "these APIs may not be in future releases of Exchange beyond E12" is a tad confusing. Unless there's not going to be a new version of Exchange for ten years after E12. That would then make sense.
Since E'rage 12 is going to use DAV, how does web services benefit E'rage users?
Is DAV going to still be a "main" access protocol ala MAPI, or is it going to be like IMAP and POP, and something that you have to do extra work to use? (Note: please keep in mind that a lot of Exchange administrators are, to old line email administrators, on the ignorant side, and if it takes more than the basic install and setup to use, they really fight using it. I had one offer to buy me an Apache box rather than go through the rather trivial work to enable multiple internet email aliases in Exchange 2000. Of course we only finished migrating off of Exchange 5.5 last year. Did I mention that Exchange administrators can be odd sometimes?)
This isn't theoretical...E'rage users are not just sitting in a design dept. somewhere. One of them is the #2 person at my company. if he's not happy, the company's not happy. (and yes, I'm pretty much ecstatic with SP2...he's FINALLY, FINALLY going to drop that abomination that is Now Contact and Up To Date 5 with the improvements in SP2)
But answering these questions now, in a clear manner will alleviate tons of problems when E12 comes out. It's always easier to say "Here, read (link) when someone asks "What are the issues with E'rage 2004/12 and Exchange 12" than it is to try and guess based on what you can scrounge out of multiple exchange - related blogs. That in turn helps you avoid that glassy stare y'all get at Macworld when you hear the same exchange question for the humpty thousandth time.
Oh yeah, and everyone doing Entourage supports owes you guys beer for the Entourage web log. Now a post or two about what E12's changes mean there would get that upgraded to good beer ;-)
But, and you know a lot of this already, getting this kind of information out of y'all is sometimes a bit...tedious?
However, since you're going to be using DAV primarily in E'rage 12, then what does this rather confusing sentence mean:
"The introduction of the new web services has freed us to “de-emphasize” three of the APIs introduced in previous generations of Exchange. These de-emphasized API’s will be fully supported in E12 (i.e. existing applications will work unchanged), and will be supported for 10 years after E12 releases, based on our standard Microsoft Support Lifecycle. These APIs may not be in future releases of Exchange beyond E12."
Does this mean no more DAV in Exchange post - 12, or that it's going to be there until 2015 regardless of version?
How are the APIs that won't work at all affect Entourage?
What does "work unchanged" mean? Is it a freezing of capabilities of that API ("nothing new will be available to DAV in E12"), a limited set of features ("these new features will be available to DAV, but no others").
Saying "support for ten years" and then in the same sentence saying, "these APIs may not be in future releases of Exchange beyond E12" is a tad confusing. Unless there's not going to be a new version of Exchange for ten years after E12. That would then make sense.
Since E'rage 12 is going to use DAV, how does web services benefit E'rage users?
Is DAV going to still be a "main" access protocol ala MAPI, or is it going to be like IMAP and POP, and something that you have to do extra work to use? (Note: please keep in mind that a lot of Exchange administrators are, to old line email administrators, on the ignorant side, and if it takes more than the basic install and setup to use, they really fight using it. I had one offer to buy me an Apache box rather than go through the rather trivial work to enable multiple internet email aliases in Exchange 2000. Of course we only finished migrating off of Exchange 5.5 last year. Did I mention that Exchange administrators can be odd sometimes?)
This isn't theoretical...E'rage users are not just sitting in a design dept. somewhere. One of them is the #2 person at my company. if he's not happy, the company's not happy. (and yes, I'm pretty much ecstatic with SP2...he's FINALLY, FINALLY going to drop that abomination that is Now Contact and Up To Date 5 with the improvements in SP2)
But answering these questions now, in a clear manner will alleviate tons of problems when E12 comes out. It's always easier to say "Here, read (link) when someone asks "What are the issues with E'rage 2004/12 and Exchange 12" than it is to try and guess based on what you can scrounge out of multiple exchange - related blogs. That in turn helps you avoid that glassy stare y'all get at Macworld when you hear the same exchange question for the humpty thousandth time.
Oh yeah, and everyone doing Entourage supports owes you guys beer for the Entourage web log. Now a post or two about what E12's changes mean there would get that upgraded to good beer ;-)