•
It has been a while since I last wrote on my experiences implementing code that consumes Broadsoft events. I’ve been reworking the code, upgrading it to version 19 of the spec, and I noticed an improvement since version 18. That’s what this post is about.
•
A quick post on Broadsoft XSI again. Why? Well, because it’s an interesting subject. I learned that there are not too many people actually developing to it. So here’s something about testing the software, assuming you’re developing against RoutIt VOIP platform.
•
I wrote about the specifics I encountered with the Broadsoft XSI API before, in this post. I didn’t mention the software I used to support the development of the application. This post will be about what I did to consume data produced by the XSI environment
•
XING aims to be a platform for business professionals, offering a platform through which supply meets demand. They seem to be quite good at it. Take a moment to review the services they’re offering and judge for yourself. I think of them mainly as an European competitor to LinkedIn® and they have an API…
•
The Satellite XMLRPC API is a complete API, allowing management of the most common objects within the Satellite. It allows CRUD operations on channels, configuration channels, kickstart profiles, kickstart snippets, configuration files, etc. It’s organized using namespaces. Every trained developer will find his (or her) way in a moment.
•
I have been developing a tool which integrates a LinkedIn profile into WordPress. That’s not complicated because LinkedIn has an API which enables access to a LinkedIn users’ data. This API has great documentation and examples, which invites you to give it a try.