When testing the datasift ruby gem locally be sure to turn SSL off

Here's how to go about not getting caught out with this

I am getting to play with the awesome DataSift service as part of a project I am working on in Rumble and I was coming across some weird issues when testing locally, basically the consume would start but never actually get anywhere, it would create the connection but not fail or return anything, it would just sit there.

The fix that worked for me isn't something I would recommend in production, but for local testing I just turned off the need to use SSL for the user object.

So when I create my user like this;

@user  = DataSift::User.new("#{username}", "#{api_key}")

I then call the following;

@user.enableSSL(false)

Now when I do something like;

@consumer = @user.getConsumer(DataSift::StreamConsumer::TYPE_HTTP, 'my_stream_hash')
@consumer.consume(true) do
    ...
end

Everything works as expected :-)

Recent posts View all

Ruby

History of Ruby Programming Language

The history of the Ruby programming language

Management

What I look for in a CTO

There are eight things I always look for when deciding if someone would make a good CTO