tag:blogger.com,1999:blog-4740937111045053616.post8579411603522219789..comments2023-06-02T10:27:57.896+01:00Comments on The Fletcher Project: Introducing Sporting Index Super Simple IntegrationAnonymoushttp://www.blogger.com/profile/11975739524615592926noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4740937111045053616.post-16238308418988927592009-12-17T11:01:14.402+00:002009-12-17T11:01:14.402+00:00Thanks for the question Jan
We considered XMPP an...Thanks for the question Jan<br /><br />We considered XMPP and that could have been a valid choice for us. Things like ActiveMQ etc wouldn't have been as suitable because our goal here was a totally portable integration. Proprietary messaging systems tend to need specific clients which are difficult to enforce when you don't have control or influence over the remote side (our customers are a large collection of heterogeneous implementations belonging to totally separate organisations).Anonymoushttps://www.blogger.com/profile/11975739524615592926noreply@blogger.comtag:blogger.com,1999:blog-4740937111045053616.post-77157712870225230862009-12-16T22:31:00.950+00:002009-12-16T22:31:00.950+00:00Hi Eachan,
I like the way you wrapped a pubsub sy...Hi Eachan,<br /><br />I like the way you wrapped a pubsub system in HTTP. I would be interested in hearing why you didn't choose a "real" messaging system for your clients to connect to. Jabber or some AMQP implementation like ActiveMQ or RabbitMQ spring to mine. Nothing against your approach, however there are specialized systems for this.Janhttp://www.managingtech.denoreply@blogger.com