Eloqua PHP SDK
As part of our continuing open-source efforts here at Splunk, we’ve released the Eloqua PHP SDK that we’re using internally under the Apache License, version 2. We’re always very excited whenever we can contribute code back to the community, and this is certainly no exception! The SDK abstracts away a lot of the complexity inherent in dealing with SOAP, allowing developers to focus strictly on the API itself. The SDK also provides a workaround for a PHP bug in the native SOAP client where constructors don’t get called when instantiating classes mapped to SOAP types.
Splunkbase, a project near and dear to my heart, has re-launched on splunkbase.com. Behind the scenes, Splunkbase has been running all along, as it is what handles app browsing and installation in the product, but we’re thrilled to open the site once again to the community, as the redeployment of Splunkbase was requested by Splunkers around the world. For those folks who have never visited the site, it’s our interface to share Splunk Apps you’ve built with the community, and to download apps built by fellow community members, Splunk partners, and Splunk engineers here at HQ.
We’ve given a facelift to most areas of the site, but we’ve kept the previous 3.x UI active under the Archive tab, …
Python and Salesforce
Well, a few months ago, a couple of the support folks asked me about the feasibility of creating cases in Salesforce through the command line in Python, and after doing a bit of research, I realized (surprisingly) that there really wasn’t a good way to use the Salesforce API in Python *if* you want to parse a WSDL (There is an excellent package called Beatbox if you don’t want or need to parse the XML). There is a very good Python SOAP client out these days called Suds, which unlike ZSI and SOAPpy is able to handle SOAP namespace prefixes (a key for handling Salesforce’s WSDLs), but it doesn’t handle the nitty-gritty details of the SOAP interaction for you …