Proton status update 2013-05-10Comment edited by Ken Giusti :Changes (1)
Full ContentI've been working on a demo based on Messenger. The goal is to build a simple RPC client/server that will operate over an unreliable mesh of dispatch-routers. The goal is to achieve "exactly once" message delivery using only the messenger api (at the clients), over an unreliable multi-hop mesh of amqp "routers". To be clear - the routers offer no persistence, they merely forward the message and propagate back the delivery status (see qpid/extras/dispatch/router source code for all the gory details). In doing this I hope to identify any weaknesses or missing features in the current api or documentation for messenger. For now the client code is available on github - see the fortune directory in https://github.com/kgiusti/proton-tools
Change Notification Preferences
View Online
|
|
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence
- [CONF] Apache Qpid > Proton status update 2013-05-10 confluence