No subject

their focus is the ability to deliver a message immediately and report an
error if they cannot contact the server.

Implementing messaging from a M2M platform, there will be times when there
is no communication between the client and the server...but the application
may still want to submit messages which should be queued until such time as
the "local queue" so to speak can contact the server and delivery the
messages.

In summary, leaving the "retry/retransmission" of message to the
messaging infrastructure...rather then have the application monitor/poll
connectivity to the server.

Is something like this possible?


Thanks
Bruce

--90e6ba6e8be400adb3049f4d6a11
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi<div><br></div><div>I was wondering what others are doing with regards to=
 &quot;queuing&quot; local messages for deliver when the network is availab=
le.</div><div><br></div><div>From my limited experience playing to &quot;ra=
bbitmq-c client&quot; and Python &quot;pika&quot;, their focus is the abili=
ty to deliver a message immediately and report an error if they cannot cont=
act the server.=A0</div>
<div><br></div><div>Implementing messaging from a M2M platform, there will =
be times when there is no communication between the client and the server..=
.but the application may still want to submit messages which should be queu=
ed until such time as the &quot;local queue&quot; so to speak can contact t=
he server and delivery the messages.=A0</div>
<div><br></div><div>In summary, leaving the &quot;retry/retransmission&quot=
; of message to the messaging=A0infrastructure...rather then have the appli=
cation monitor/poll connectivity to the server.</div><div><br></div><div>
Is something like this possible?</div><div><br></div><div><br></div><div>Th=
anks</div><div>Bruce</div><div><br></div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div>

--90e6ba6e8be400adb3049f4d6a11--