We are back with a solution to another, perhaps not so widely known bug. This time it’s a ColdFusion native bug involving its own websocket and session variables. Frankly, it was bugging us (no pun intended) for the past 2 years. Here’s the problem in detail:
We are running an application that utilises ColdFusion’s native websockets functionality. In a most basic scenario, we run a cfcomponent with several functions to create a notification record and insert it in the database. Then, as one would, push it via the webscoket so all the connected users with the relevant permissions receive it instantaneously. All is nice and well, right? NO.
It’s been a while now that we were searching for a working ColdFusion LinkedIn API that would let users not only to receive data, but to submit some too. Although there were optional libraries such as linkedin-j, not everyone knows or wants to dip into the pure java world. Thanks to Derek Bowes, we stumbled across the LinkedIn.cfc which was a great plugin. The only trouble was that the plugin was already out of date since LinkedIn had updated their API in the second half of 2012, and now required member permissions were no longer a part of the original source code.
So we took the initiative to our hands and amended the plugin to allow users set the permissions required as well as the ability to post status updates.
Ever tried to create an AJAX-style ColdFusion file upload form which executes without reloading the page? This is our take on this widely popular technique. With the help of ColdFusion, jQuery and ’hidden’ iframe the following tutorial will show you how exactly you can achieve this.