tag:blogger.com,1999:blog-4338956765494283322.post99554450595615718..comments2024-03-29T19:35:03.327+08:00Comments on Bill Poole's Creative Abrasion: Synchronous Request/Reply is Bad (continued...)Billhttp://www.blogger.com/profile/12877394913101625095noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4338956765494283322.post-78372173971890380832022-07-30T15:20:39.257+08:002022-07-30T15:20:39.257+08:00Visit This Link b7z92z5z10 replica gucci replica b...Visit This Link b7z92z5z10 <a href="https://www.dolabuy.ru/" rel="nofollow"><strong>replica gucci</strong></a> replica bags joy replica bags joy <a href="https://www.dolabuy.ru/gucci-c-157_168/" rel="nofollow"><strong>replica gucci handbags</strong></a> i0f67e0k98 replica bags ebay replica bags and watches <a href="https://www.dolabuy.ru/handbags-c-157/" rel="nofollow"><strong>you can try here</strong></a> e2y04u8i86 best replica bags online 2018Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4338956765494283322.post-57099741937280348002008-12-18T04:21:00.000+09:002008-12-18T04:21:00.000+09:00Wouldn't the question of how/if message retries ar...Wouldn't the question of how/if message retries are handled be related the the technology in use and not the more broad request-reply concept? In other words, you make it sound like it would be impossible for a message passing technology to exist that offered synchronous delivery while also handling deivery retries. Is that the case? My question also applies to error handling and guaranteed single delivery.<BR/><BR/>Note that I agree with your other anti-synchronous point about keeping too many threads alive.Anonymousnoreply@blogger.com