Fixed Twitter Feed and Added Listening Links

So since Twitter updated their API, the way that this them pulls feeds wasn’t working anymore, it was really archaic anyway.  Well instead of using one of their embed widget things I created a service on another server of mine that allows for pulling of your last tweets.  You simply give it and it will return XML with your five last tweets, it works from one to twenty.  I currently have the API caching the calls so it doesn’t have completely live data.  I built the service using perl dancer and starman as the server and memcached for caching.  More of an exercise then anything else.

Also added a link category of Listening/Listened to post the current audio books I’m listening to.  I’m a big fan of and the authors that put their stuff up there, so I thought I would share what I’ve listened to.  A good place to start is with authors Nathan Lowell and Scott Sigler.  Their stuff is also available on (Nathan Lowell, Scott Sigler).

PHP, Perl, Apache, Dancer, Starman and Beanstalkd – When our powers combine!

That is a mouthful, it almost sounds like a super hero team roster.  In fact I think Apache and Starman are super heroes, or at least are in comics.

So what am I doing with all of these things?  I am planning on using them together for a new side project I am working on.  At first glance it doesn’t seem to make sense, I mean who would choose to use two different languages (PHP, Perl) and two different web servers (Apache, Starman)?  Why would I not just use PHP and Apache or use Perl/Dancer and Starman.  The reason is speed of coding mainly, PHP is my primary language, then after that is Perl and third is Java but that’s not related to this.  So the mashing of services to is to provide a quick yet robust solution while also challenging me enough to learn some new things to keep my interest.

The Break Down:

  • PHP & Apache will handle the main site and crud
  • Apache will proxy out to Starman (this will allow for easier separation when needed)
  • Perl using Dancer and Starman will handle the incoming API calls; validating, parsing and pushing the result to beanstalkd
  • Beanstalkd workers will most likely written in PHP to leverage the framework I’m using, but can be written in Perl

Breaking that out is not really convincing that running the API with Perl, Dancer and Starman is the right thing when it’s all on the same server.  An advantage of doing this is mitigating my mistakenly exposing anything since it doesn’t talk to the main PHP site directly.  Makes a little more sense when we separate the API out, I wouldn’t want to have to replicate the PHP server for simple things the API is doing.

Project links: PHP, PerlApache, Dancer, Starman, Beanstalkd

Go back to top