Now that we have succeeded in creating, updating and deleting calendar items and mastered Exchange Impersonation, it’s time to turn our attention to having Exchange notify us about what it is doing. Part 4 of this series is going to provide a detailed code walk-through of some code that leverages the Subscription API.
The example includes two code examples – one for Java programmers and one for OpenEdge programmers. The OpenEdge version writes updates through the OpenClient via the OpenEdge AppServer to an OpenEdge database.

Research and Innovation and Enterprise Architecture
May 12
Posted by Bruce Gruenbaum in Commentary, Enterprise Architecture, Exchange Web Services | 2 Comments
The thing that sets one business apart from another is the special added value that it brings to the table. It does something different. It has come up with an idea that no one else does quite the same way, or so the business believes. Even when someone else is doing exactly the same thing, the thing that differentiates the two is the way that they do it. This is the “special sauce” that makes a business special.
But how do companies go about finding that “special sauce?” And more importantly, what can they do to maintain it?
While I don’t believe for a second that all the special sauce in the world comes from technology, technology can often be at the very heart of making that special sauce, especially when we are talking about building customer relationships.
Technology can be a huge support in this area, and that’s where research and innovation come in. Using technology to build better business relationships is where the focus of technical growth is, and learning how to apply technology to do so is where research and innovation come in. [...]
Tags: Enterprise Architecture, EWS, Exchange EWS, Innovation, Research