Activity log for bug #1585096
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2016-05-24 08:10:15 | Free Ekanayaka | bug | added bug | ||
| 2016-05-24 08:10:23 | Free Ekanayaka | txamqp: status | New | In Progress | |
| 2016-05-24 08:10:27 | Free Ekanayaka | txamqp: assignee | Free Ekanayaka (free.ekanayaka) | ||
| 2016-05-24 08:11:14 | Free Ekanayaka | branch linked | lp:~free.ekanayaka/txamqp/client-service | ||
| 2016-05-27 13:07:41 | Free Ekanayaka | summary | Add an AMQService class for applications needing to be permanently connected | Add an AMQEndpoint for getting an authenticated AMQClient | |
| 2016-05-27 13:10:02 | Free Ekanayaka | description | Twisted 16.1.0 has introduced the ClientService facility which is meant to replace the deprecated ReconnectingClientFactory, and use more modern APIs like endpoints. It'd be nice to have an AMQService that subclasses ClientService and takes care of authenticating, so that applications like lp:txlongpoll don't have to always implement equivalent code on their own. | Most consumers of txamqp typically need to go through the dance of declaring a factory, calling IReactor.connectTCP or some IStreamClientEndpoint.connect, and call AMQClient.authenticate. It'd be good to simplify this by having an AMQEndpoint that does the job. | |
| 2016-05-27 13:10:58 | Free Ekanayaka | branch linked | lp:~free.ekanayaka/txamqp/amq-endpoint | ||
| 2016-05-27 13:11:16 | Free Ekanayaka | branch unlinked | lp:~free.ekanayaka/txamqp/client-service | ||
| 2016-05-27 13:21:26 | Esteve Fernandez | txamqp: status | In Progress | Fix Committed |
