Change webjob to use a blob trigger instead of a queue message for image resize about contosomoments HOT 3 CLOSED

Furthermore, if we are looking to make this change in the API backend, we should consider issue #34

from contosomoments.

The problem is that the mobile client needs there to be a record when it does its file upload. It could potentially do the file upload first (and have the Image record only in its local database), but then we're still putting logic in the client, because it has to do the updates in a particular order.

A better solution is to just use blob triggers to do the image resize. I tried this with the latest webjobs SDK, but I still saw 10 minute latency before the blob was actually picked up. I need to investigate this further.

The other problem is that the code changes the content type of the source image during the resize, since the mobile client does not set it. This causes another blob trigger to fire, since it changes the underlying blob.

In theory, we could just remove this content type logic, since on the web, the source image is always shown in the context of an HTML page and doesn't need its own content type. The resized images do need it, but their content type is set during the resize operation.

from contosomoments.

We'll fix this by using a webjob and Azure Function with a blob trigger, so it's a dup of #42

from contosomoments.