ExportItems and UploadItems

[LukeMarlin]

Hi guys,

Do you intend to implement these two methods in EWS managed API, or will we have to stick with web calls ?

[dclaux]

No plan to do this at this time, but if you want to give it a shot you are more than welcome.

[XavierDa]

Hello, i'm going to implement it. (i'm luke co-worker)

Just to be sure i need to :

• Implement Responses
• Implement Requests
• add new functions to service

Do this sounds right ?

[LukeMarlin]

Any insight from you @dclaux @vboctor ?

[dclaux]

@XavierDa Yes, that sounds about right. Looking forward to looking at your changes.

[XavierDa]

Hello, i finished implementing it, but i have a small problem.

It seems that exportItems change ItemIds (can't find any of the itemids i sent in the result), Is there any way to find a link between them ?

[dclaux]

One caveat - The typical use case for UploadItems is read data from somewhat large files (as opposed to in-memory buffers) or from a database field. So the EWS Managed API's implementation of UploadItems should stream the data right from its source and serialize it by chunks, so that there is no need to load a full copy of all the data in memory. You can take a look at how file attachments are handled to see an example of the how the API does this.

[dclaux]

ExportItems shouldn't change any Id. It's just a dump of what's in a mailbox.

[dclaux]

So are you saying that the Ids you get in ExportItems' response aren't the same as the ones you passed in the request? Sounds really weird to me. That said the items in the response should be in the same order as those in the request, so you can match based on ordering.

[XavierDa]

Ok found my error. I had a misplaced new ItemId.

For uploadItems... i will check how it's done for file attachement and try to get a similar solution.
Right now my solution for exportItem returns a byte[] for data, maybe it should use a Stream too ? (so it's easier to implement export => upload solutions ?)

[dclaux]

Yes, ExportItems should also use streams.

[dclaux]

Thinking more about this - ExportItems needs to be passed a callback method that lets the developer specify the stream for each item in the response. Either that, or introduce an "ExportManager" class that encapsulates the entire logic and exposes an event that lets developers specify the destination stream for each item. I can think of two main ways a developer might want to store what ExportItems produces: 1) one file/database row/field per item, or 2) a single file that stores all items. I think the API should make it easy to do either.

[Biztactix-Ryan]

How far did you get with this? @XavierDa

[XavierDa]

We have a working version here, but we never manage to make a PR due to some slight hiccups on our side.

if you want this you can get it from this pull request #109

[jrouzies-fr]

@XavierDa , are we sure it is working?

I can get the data without issue, but the UploadItem doesn't seem to do anything on the target mailbox / service

Source mailbox Inbox:

Target mailbox Inbox: