[rt-devel] [PATCH] Use Content-ID when handling multipart message over REST.

[Arkadiusz Miśkiewicz]

On Friday 20 of February 2015, Arkadiusz Miśkiewicz wrote:
> From: Przemyslaw Plewa <przemyslaw.plewa at domena.pl>
> 
> Record Content-ID identifier that came over REST API.
> 
> This allows us to have multipart messages with one (or more) part
> refering to other parts of message. Content-ID identifier is used for
> reference.
> 
> Such message also needs multipart/related type (instead of default (in
> rt) multipart/mixed. So if we detect Content-ID in any part of multipart
> message we switch Content-Type to multipart/related.

There is also pull request with it if that way is better

https://github.com/bestpractical/rt/pull/136

Also I'm attaching a test script to show how created message looks like (one 
mime part refers to second mime part (attached image) via content-id).

Please review and merge.

Thanks,
-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.php
Type: application/x-php
Size: 1857 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-devel/attachments/20150220/33cd4303/attachment.bin>