<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Le 2013-05-15 � 10:37, Michael Klishin a �crit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/5/13 Fran�ois Beausoleil <span dir="ltr"><<a href="mailto:francois@teksol.info" target="_blank">francois@teksol.info</a>></span><br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
When the request hits the web server process, is it expected that it would open a channel, create a server-named queue and send the request, with reply-to set to the queue?</blockquote></div><br><div style="">I'm not sure I understand the "optional data" part. Could you elaborate?</div></div></div></blockquote><br></div><div>If the UI is missing that data, then it's no big deal. It's a best-effort.</div><div><br></div><div>Thanks for validating my reasoning. I'll probably skip the network round-trip for the channel, since that will give me a bit more time to do other, more important, work.</div><div><br></div><div>Bye!</div><div>Fran�ois</div></body></html>