Everyone is very excited about chatbots as the future of messaging, customer service, information delivery, etc. Facebook touts Messenger bots as AI (e.g. Jarvis) and the press gets excited about how they will change the world. But really, bots are essentially an ESB that listens for keywords and routes responses back to the user. This project will show you how to build one using Anypoint Platform.
I’m no psychic but I bet you two things: This holiday you already took a bunch of pictures that went straight into facebook and you drank A LOT. Now you’ll probably edit your photos in the morning, but it seems a shame to lose those drunken shots. What if you could save them? Let’s see how you can do that using Mule. We’ll see how we can make an app that pulls all our facebook photos and upload them into box.
This tutorial is the second in a series of blog posts that explain how to integrate Mule and Social Media.
Today’s post will focus on connecting to Facebook and updating your status on facebook.
Other posts to expect will integratie Mule and:
There was a lot of buzz a few years ago around real-time web and since then it has been bubbling along. I have a financial/enterprise background so real-time has a very different meaning to me; time is measured in microseconds. Web real-time seems to be measured as sub 1 second . My issue with real time web to date is only parts of the web are web-real time. While the data can be delivered to the browser using push technologies such as comet and web sockets, the vast majority of REST and soap API that provide access to application data still use the HTTP request response model.
That’s starting to change with more public streaming APIs appearing. A streaming API (aka HTTP Push) works by the client opening a socket, providing some criteria of the data it wants to receive and the server will deliver new data as it is received over the open socket. For those familiar with publish-subscribe models of delivering data, this all sounds familiar.