tag:blogger.com,1999:blog-8840085855436806841.post524007560572447670..comments2009-12-15T19:56:15.841-05:00Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8840085855436806841.post-26358242930372208562009-12-15T19:56:15.841-05:002009-12-15T19:56:15.841-05:00scranthdaddy&#39;s suggestion seems much more robust to me. It would be ideal if someone provided an extension to Typica that did this automatically.Steven Loeppkyhttp://www.blogger.com/profile/01948718143411566664noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-62280261312609265822009-11-14T12:27:26.182-05:002009-11-14T12:27:26.182-05:00I overcame the size limit in a different way. If the message body is less than 8K, I store it in its entirety. If it is larger than 8K, I store the body in S3, and store the key in the message queue body using a typographical convention such as __S3_KEY_ID:blah<br /><br />Then I check the message body upon retrieval. If it begins with __S3_KEY_ID then I know to look for the data in S3. Otherwise, it is entire body and I process it accordingly.<br /><br />hope this helps!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-53714630258075460732009-11-11T01:14:18.690-05:002009-11-11T01:14:18.690-05:00Great post. I initially saw the message size limitation as a deal breaker but I am glad to see how you have circumvented that. Thanks!scranthdaddyhttp://www.blogger.com/profile/18065282770040445717noreply@blogger.com